-
Notifications
You must be signed in to change notification settings - Fork 2.1k
[Tracker] MSBuild conversion issues #5482
Comments
@srivatsn this is an interesting issue for us to track... |
Status:
All issues found are listed above. Will continue migrating test projects when the vstest migration issues have been resolved. |
/cc @balachir |
Adding this guy: dotnet/sdk#480 - Facades from desktop framework targeting pack are not emitted to .deps.json for PreserveCompilationContext Essentially |
Here's another one to add: dotnet/sdk#495 PackageReference to contentFiles package breaks compilation of 'net45x' tfms |
It may be interesting to also track the CLI teams own attempts to migrate this repo: https://github.com/dotnet/cli/issues/5378 |
- Allow >= RC3 CLI's to build and run MVC. - Added extra sln's so they could be opened in VS. Currently VS' project system can't currently handle Mvc.sln. - Worked around several dotnet migration issues. They are listed in the re-attempted migration section here: #5482 - One large feature bit that couldn't be worked around was the functional tests running on desktop; it represented several known vstest issues. Removed desktop running of functional tests. - Skipped an ActionContextAccessor test due to a vstest appdomain problem.
- Allow >= RC3 CLI's to build and run MVC. - Added extra sln's so they could be opened in VS. Currently VS' project system can't currently handle Mvc.sln. - Worked around several dotnet migration issues. They are listed in the re-attempted migration section here: #5482 - One large feature bit that couldn't be worked around was the functional tests running on desktop; it represented several known vstest issues. Removed desktop running of functional tests. - Skipped an ActionContextAccessor test due to a vstest appdomain problem.
- Allow >= RC3 CLI's to build and run MVC. - Added extra sln's so they could be opened in VS. Currently VS' project system can't currently handle Mvc.sln. - Worked around several dotnet migration issues. They are listed in the re-attempted migration section here: #5482 - One large feature bit that couldn't be worked around was the functional tests running on desktop; it represented several known vstest issues. Removed desktop running of functional tests. - Skipped an ActionContextAccessor test due to a vstest appdomain problem.
- Allow >= RC3 CLI's to build and run MVC. - Added extra sln's so they could be opened in VS. Currently VS' project system can't currently handle Mvc.sln. - Worked around several dotnet migration issues. They are listed in the re-attempted migration section here: #5482 - One large feature bit that couldn't be worked around was the functional tests running on desktop; it represented several known vstest issues. Removed desktop running of functional tests. - Skipped an ActionContextAccessor test due to a vstest appdomain problem.
- Allow >= RC3 CLI's to build and run MVC. - Added extra sln's so they could be opened in VS. Currently VS' project system can't currently handle Mvc.sln. - Worked around several dotnet migration issues. They are listed in the re-attempted migration section here: #5482 - One large feature bit that couldn't be worked around was the functional tests running on desktop; it represented several known vstest issues. Removed desktop running of functional tests. - Skipped an ActionContextAccessor test due to a vstest appdomain problem.
Hey, @rrelyea, please check out the NuGet issues above. |
- Allow >= RC3 CLI's to build and run MVC. - Added extra sln's so they could be opened in VS. Currently VS' project system can't currently handle Mvc.sln. - Worked around several dotnet migration issues. They are listed in the re-attempted migration section here: #5482 - One large feature bit that couldn't be worked around was the functional tests running on desktop; it represented several known vstest issues. Removed desktop running of functional tests. - Skipped an ActionContextAccessor test due to a vstest appdomain problem.
- Allow >= RC3 CLI's to build and run MVC. - Added extra sln's so they could be opened in VS. Currently VS' project system can't currently handle Mvc.sln. - Worked around several dotnet migration issues. They are listed in the re-attempted migration section here: #5482 - One large feature bit that couldn't be worked around was the functional tests running on desktop; it represented several known vstest issues. Removed desktop running of functional tests. - Skipped an ActionContextAccessor test due to a vstest appdomain problem.
- Allow >= RC3 CLI's to build and run MVC. - Added extra sln's so they could be opened in VS. Currently VS' project system can't currently handle Mvc.sln. - Worked around several dotnet migration issues. They are listed in the re-attempted migration section here: #5482 - One large feature bit that couldn't be worked around was the functional tests running on desktop; it represented several known vstest issues. Removed desktop running of functional tests. - Skipped an ActionContextAccessor test due to a vstest appdomain problem.
This doesn't exactly block our migration but NuGet/Home#4689, .csproj file not updated in Visual Studio until user does a Save All or closes solution will certainly cause developer confusion going forward. We often flip back and forth between command line and Visual Studio. |
- Allow >= RC3 CLI's to build and run MVC. - Added extra sln's so they could be opened in VS. Currently VS' project system can't currently handle Mvc.sln. - Worked around several dotnet migration issues. They are listed in the re-attempted migration section here: #5482 - One large feature bit that couldn't be worked around was the functional tests running on desktop; it represented several known vstest issues. Removed desktop running of functional tests. - Skipped an ActionContextAccessor test due to a vstest appdomain problem.
- Allow >= RC3 CLI's to build and run MVC. - Added extra sln's so they could be opened in VS. Currently VS' project system can't currently handle Mvc.sln. - Worked around several dotnet migration issues. They are listed in the re-attempted migration section here: #5482 - One large feature bit that couldn't be worked around was the functional tests running on desktop; it represented several known vstest issues. Removed desktop running of functional tests. - Skipped an ActionContextAccessor test due to a vstest appdomain problem.
- thanx to @NTaylorMullen for initial conversion - e.g. AssemblyInfo.cs files were already minimized or removed :) - allow `>=` RC3 CLI's to build and run MVC - work around several dotnet migration issues; see #5482 - disable full .NET Framework runs of functional tests; see #5873 - remove `Microsoft.DotNet.InternalAbstractions` and `System.Xml.XmlDocument` dependencies - remove project.json (!!), *.xproj, .notest, and web.config files Redo earlier changes: - apply test migration to .NET 4.5.2 in *.csproj world - see 63507c8 for previous, project.json work - apply dependency version downgrade from 0097e40 in *.csproj world Make other test-related changes: - make Microsoft.AspNetCore.Mvc.TestDiagnosticListener a regular class library - add support for `/p:GenerateBaselines=true` for functional and Razor.Host tests - separate `GetCSharpTypeName_ReturnsCorrectTypeNames_ForOutParameter()` test - work around inability to deserialize a odd `ref` type - xUnit and vstest now serialize / deserialze test data more often - skip poor test mentioned in #5768 - work around microsoft/vstest#392 - rename tests to avoid duplicates - work around microsoft/vstest#419 - set up created `AppDomain`s with current `ApplicationBase`
@NTaylorMullen I guess we can close this right?? |
@Eilon I'd say ya. There's still some open issues above but those are tracked elsewhere. |
This is just to track all the issues that I've run into so we can capture when they're resolved.
--skip-backup
<OutputType>Exe</OutputType>
. OutputType in test project templates microsoft/vstest#287Bugs found after re-attempting migrate (In Progress...):
https://github.com/dotnet/cli/issues/5407, https://github.com/dotnet/cli/issues/5318SkipCompilerExecution Error dotnet/project-system#1554, ProjectInstance based build fails with a "Target not found exception" when the instance is mutated dotnet/msbuild#1726Contents of string '{test name}' exceeds max of '449', string has been truncated.
messages Long test data results inContents of string '{test name}' exceeds max of '449', string has been truncated.
messages xunit/xunit#1139dotnet run
doesn't handle ctrl-c well dotnet/cli#812dotnet msbuild
commands hang with some command-line redirectionsdotnet/cli#5849dotnet msbuild
commands sometimes hang after writing MSBuild_*.failure.txt filesdotnet msbuild
commands sometimes hang after writing MSBuild_*.failure.txt files dotnet/msbuild#1808testhost
Binding Redirects necessary to run Unit Tests on .NET Framework are not preserved when running intesthost
microsoft/vstest#428The text was updated successfully, but these errors were encountered: