Web Projects Build Support

[Nirmal4G]

Update: Blocked by project system. M$FT is bringing classic projects to open in CPS.

[clairernovotny]

Closing as old.

[jzabroski]

@Nirmal4G @clairernovotny While this issue is closed, I'm curious if MSBuild.Sdk.Extras supports ASP.NET Classic? In #60, @clairernovotny explained the blocking issue was related to launching IIS Express and attaching the debugger via MSBuild, and that in order for this to work, it has to be part of the core SDK support (I'm not clear on that assumption/statement and why it can't be added in a way similar to AttachToAnything Visual Studio plug-in works - I've created similar hooks for debugging PowerShell binary cmdlet projects).

[Nirmal4G]

VS Team is currently working to support legacy projects opening in CPS.

I have WFF/ASP/WPF limited support in my fork of this sdk for my own projects. It's hacky and I don't recommend anyone to use it in production projects.

However, if you want to cleanup the ItemGroups in the project file. You can use my MSBuild.NET.DefaultItems.

[jzabroski]

@Nirmal4G Whoa, MSBuild.NET.DefaultItems sounds interesting.

Can I ask you a few questions for my own education?

1. Before today, I always assumed that the SDKs were limited to the ones mentioned in Microsoft Docs at .NET Core project SDKs
2. The MSBuild.NET.DefaultItems seems to point a way forward for me to create my own SDK fairly easily.
3. In particular, as co-maintainer of FluentMigrator, it would be nice for "Database migration assemblies" for people to set an Sdk="FluentMigrator.Sdk" which will change the out-of-the-box auto-globbing rules of the Microsoft.Net.Sdk - is that possible and am I starting to understand the possiblities of this project and your fork here?
4. Is this project still actively maintained - or should I be following your fork instead? Your last commit is within the last month, vs. this project last updated >6 months ago.

[Nirmal4G]

1. Custom SDKs are relatively a new concept. Their design is not complete. So, they are not advertised as heavily as other package types.

2. It doesn't work with <Project Sdk=""/>. I created them specifically for globbing, so you have import it manually within the project file.

3. If you're interested in Sdks, look at my other Sdks and @microsoft has official MSBuildSdks.

4. This is active, always use this one over mine.

Mine's not official open source project. They are ideas, I use in my own projects. That's also the reason they are not documented yet.

But my colleagues have expressed interest in default globbing, so I created it for them. Again, not for production!!

As this thread is going off topic, Create an issue in my repo, if you have any Qs regarding the Sdks.