Skip to content
This repository has been archived by the owner on Dec 14, 2018. It is now read-only.

[Tracker] MSBuild conversion issues #5482

Closed
36 of 55 tasks
NTaylorMullen opened this issue Nov 1, 2016 · 10 comments
Closed
36 of 55 tasks

[Tracker] MSBuild conversion issues #5482

NTaylorMullen opened this issue Nov 1, 2016 · 10 comments

Comments

@NTaylorMullen
Copy link
Member

NTaylorMullen commented Nov 1, 2016

This is just to track all the issues that I've run into so we can capture when they're resolved.


Bugs found after re-attempting migrate (In Progress...):

@danroth27 danroth27 added this to the 1.2.0 milestone Nov 2, 2016
@TheRealPiotrP
Copy link

@srivatsn this is an interesting issue for us to track...

@NTaylorMullen
Copy link
Member Author

Status:

  • Migrated MVC src projects with work arounds.
  • Migrated MVC sample project with work arounds.
  • Migrated 1.5 MVC test projects but stopped due to the time spent working around known issues.

All issues found are listed above. Will continue migrating test projects when the vstest migration issues have been resolved.

@NTaylorMullen
Copy link
Member Author

/cc @balachir

@NTaylorMullen
Copy link
Member Author

NTaylorMullen commented Dec 12, 2016

Adding this guy: dotnet/sdk#480 - Facades from desktop framework targeting pack are not emitted to .deps.json for PreserveCompilationContext

Essentially preserveCompilationContext = true doesn't always work so any semi-advanced View will explode at runtime if run on the desktop framework. /cc @Eilon for visibility

@natemcmaster
Copy link
Contributor

Here's another one to add: dotnet/sdk#495 PackageReference to contentFiles package breaks compilation of 'net45x' tfms

@natemcmaster
Copy link
Contributor

It may be interesting to also track the CLI teams own attempts to migrate this repo: https://github.com/dotnet/cli/issues/5378

NTaylorMullen added a commit that referenced this issue Jan 31, 2017
- 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.
NTaylorMullen added a commit that referenced this issue Jan 31, 2017
- 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.
NTaylorMullen added a commit that referenced this issue Feb 1, 2017
- 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.
NTaylorMullen added a commit that referenced this issue Feb 2, 2017
- 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.
NTaylorMullen added a commit that referenced this issue Feb 2, 2017
- 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.
@dtivel
Copy link

dtivel commented Feb 3, 2017

Hey, @rrelyea, please check out the NuGet issues above.

NTaylorMullen added a commit that referenced this issue Feb 8, 2017
- 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.
NTaylorMullen added a commit that referenced this issue Feb 9, 2017
- 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.
dougbu pushed a commit that referenced this issue Feb 23, 2017
- 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.
@dougbu
Copy link
Member

dougbu commented Feb 25, 2017

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.

dougbu pushed a commit that referenced this issue Feb 26, 2017
- 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.
dougbu pushed a commit that referenced this issue Feb 26, 2017
- 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.
dougbu pushed a commit that referenced this issue Mar 1, 2017
- 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`
@Eilon
Copy link
Member

Eilon commented Mar 22, 2017

@NTaylorMullen I guess we can close this right??

@NTaylorMullen
Copy link
Member Author

@Eilon I'd say ya. There's still some open issues above but those are tracked elsewhere.

@Eilon Eilon closed this as completed Mar 22, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants