-
Notifications
You must be signed in to change notification settings - Fork 354
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix loc build #33
Comments
We should make sure we are building the satellite resources (even if that means disabling localized template builds #47). |
You don't need to build any tooling from this branch. VS tooling has been building in separate branches without the runtime for the last 4 years. No active localization work has been done in Main since probably 2013 when WSR2 Refresh shipped. |
Plan revision: Don't worry about the lack of localized resources for the PCL and .NET Standard assemblies. Focus on getting a clean build. |
Completed with TFS check-ins and DI configuration changes. |
Not sure localized builds of the template projects are working on the CI. Certainly, Web Stack Runtime / Main.Signed.AllLanguages builds succeed only because
lsbuild.exe
errors like the following are ignored:…
…
FYI the above errors occur because the
@model
directives contain$safeprojectname$
in the type names. Probably need to substitute another token before calling the Razor parser and restore$safeprojectname$
after.And the response files aren't 💯% correct:
Separately,
Microsoft.AspNet.WebApi.Client.fr
packages are available on http://www.nuget.org but not in our nightly CI feed on http://www.myget.org. This is more likely about nightly build configuration than anything else because the packages are created and signed in the CI builds. But is that configuration correct?The text was updated successfully, but these errors were encountered: