You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Could somebody from the container tools team have a look at this issue?
MSBuild.SDK.SystemWeb is an MSBuild SDK designed to allow for the easy creation and use of SDK (shortform) projects targeting ASP.NET 4.x using System.Web.
It has been made with all the input from this very popular issue on the dotnet/project-system repo.
Almost everything is working in the new SDK style project exactly like it used to work before. Except for adding docker support.
We have it almost working by adding a few things manually after creating a bare "file > new project".
When trying to debug the project in docker, the container seems to get built fine, it even starts up, but then at the last part (launching the debugger) something goes wrong and we get an error Failed to find path of the output assembly for project WebApplicationSystemWeb. The same thing happens when trying to start without debugging.
I'm pretty sure we are very close to nailing this, but we can't seem to figure out what exactly is this last problem... and as we don't have the source ourselves, we will have to rely on a friendly engineer who does... ;-)
FYI: The DockerSdkStyle repository above contains 3 times the same bare "file > new project" project: one for classic ASP.NET MVC (.Net Framework), one for ASP.NET Core and then one for the MSBuild.SDK.SystemWeb (which should functionally be the same as the classic .Net Framework one). All of them have docker support added. This way they can be easily compared.
The text was updated successfully, but these errors were encountered:
@fretje I did a quick look and it appears the issue is that when the ASP.NET project is using the new SDK style the debugging goes through a different entry-point which in our case only supports .NET Core projects. We've added supporting this to our backlog.
@NCarlsonMSFT : I can you please update us if any solution for this? We also have one SDK style .Net framework 4.7 application and want to have Docker container debug support in it. Using VS 2019 but when I right click on project I don't see option to Add -> Docker support option.
Could somebody from the container tools team have a look at this issue?
MSBuild.SDK.SystemWeb is an MSBuild SDK designed to allow for the easy creation and use of SDK (shortform) projects targeting ASP.NET 4.x using System.Web.
It has been made with all the input from this very popular issue on the dotnet/project-system repo.
Almost everything is working in the new SDK style project exactly like it used to work before. Except for adding docker support.
We have it almost working by adding a few things manually after creating a bare "file > new project".
When trying to debug the project in docker, the container seems to get built fine, it even starts up, but then at the last part (launching the debugger) something goes wrong and we get an error
Failed to find path of the output assembly for project WebApplicationSystemWeb
. The same thing happens when trying to start without debugging.I'm pretty sure we are very close to nailing this, but we can't seem to figure out what exactly is this last problem... and as we don't have the source ourselves, we will have to rely on a friendly engineer who does... ;-)
FYI: The DockerSdkStyle repository above contains 3 times the same bare "file > new project" project: one for classic ASP.NET MVC (.Net Framework), one for ASP.NET Core and then one for the MSBuild.SDK.SystemWeb (which should functionally be the same as the classic .Net Framework one). All of them have docker support added. This way they can be easily compared.
The text was updated successfully, but these errors were encountered: