Remove support for legacy csproj format #816
-
The legacy csproj format, using the package.config files and thus the old project system can not handle transitive dependencies. This is a blocker for changes we're doing in V4. The current plan is now to release V4 with supporting the new SDK based csproj files only. The legacy will be supported by the 3.X series of adapters, but they will only see small simple bug fixes and updates whenever an update to Visual Studio that breaks the adapter happens. We don't see any reason why you would update the adapter, and not update your csproj files, in particular since these are "only" test projects. What do people think of this? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 3 replies
-
I'd support the change especially if it is causing problems. You will get complaints and bugs filed though. Is there a way that you can detect the old format and display a warning? |
Beta Was this translation helpful? Give feedback.
-
The legacy csproj format does not have to use the packages.config format. Legacy csproj has allowed the use of PackageReference (transitive dependencies) since around when PackageReference first appeared. If the problem is just with transitive dependencies, I think the adapter will be remaining compatible with legacy csproj, just not compatible with packages.config. |
Beta Was this translation helpful? Give feedback.
-
I don't see any problems moving forward in this direction. Like already said, there are some transient support in the old type, but also right in respect updating projects, if somebody is maintain some code on old types, they should update if possible. Are you also doing anything related to what .net frameworks you will support? Might be time to drop some of the full framework versions |
Beta Was this translation helpful? Give feedback.
I'd support the change especially if it is causing problems. You will get complaints and bugs filed though. Is there a way that you can detect the old format and display a warning?