CZEMacLeod
commented
1 year ago @julealgon A few quick notes:
- You seemed to have missed correctly creating the launchSettings.json file and thus the F5 debug didn't work in your example.
- You don't need to define
EnableWebFormsDefaultItemsas it is true by default. This is only required for specific scenarios where you don't want to use the built in globbing system. - You don't need the
Referenceitems as these are brought in automatically by the base SDK. - You don't need
AppendTargetFrameworkToOutputPathas this is set by the SDK.
<Project Sdk="MSBuild.SDK.SystemWeb/4.0.88">
<PropertyGroup>
<TargetFramework>net472</TargetFramework>
<GeneratedBindingRedirectsAction>Overwrite</GeneratedBindingRedirectsAction>
</PropertyGroup>
<ItemGroup>
<PackageReference Include="Microsoft.Web.Infrastructure" Version="2.0.1" />
<PackageReference Include="AspNet.ScriptManager.jQuery" Version="3.4.1" />
<PackageReference Include="Microsoft.AspNet.ScriptManager.MSAjax" Version="5.0.0" />
<PackageReference Include="Microsoft.AspNet.ScriptManager.WebForms" Version="5.0.0" />
<PackageReference Include="Microsoft.AspNet.Web.Optimization" Version="1.1.3" />
<PackageReference Include="Newtonsoft.Json" Version="12.0.2" />
<PackageReference Include="WebGrease" Version="1.6.0" />
<PackageReference Include="Antlr3.Runtime" Version="3.5.1" />
<PackageReference Include="Microsoft.AspNet.Web.Optimization.WebForms" Version="1.1.3"/>
<PackageReference Include="Microsoft.AspNet.FriendlyUrls" Version="1.0.2" />
</ItemGroup>
</Project>{
"iisSettings": {
"windowsAuthentication": false,
"anonymousAuthentication": true,
"iisExpress": {
"applicationUrl": "http://localhost:51867/",
"sslPort": 0
}
},
"profiles": {
"IIS Express": {
"commandName": "IISExpress",
"launchBrowser": true,
"environmentVariables": {
"ASPNETCORE_ENVIRONMENT": "Development"
}
}
}
}I can't really help beyond that - the issue with intellisense is down in visual studio and/or the compiler, not the SDK. The LSP system has fixes in place to force the old style parsing for razor pages to allow editing MVC easily, but it looks like there is something in the base VS product that doesn't handle aspx/ascx etc. files well.
I wouldn't recommend using this for 'greenfield' development (not that many people are likely to be doing that with either .net 4.x or webforms), but it is more meant to be able to build well in a CI/CD system and allow you to easily manage package updates etc. which are some of the major advantages of the new project format. I would recommend only using it to maintain an existing site, where you are most like to be doing one of 4 activities:
- Editing 'text' (or html) content in webform pages. The main reason for this is that no modification of controls etc. will work as the back end to update the .designer.cs files does not work without the old project system.
- Editing of code - intellisense should work correctly in the code behind files, and allow you to make fixes or changes to the code.
- Editing of content - css, javascript, images, etc. Again, intellisense will work for these files, and adding/altering content files is handled by the globbing to make it easier to manage the project file, especially in a team environment.
- Updating packages due to security fixes or similar. For instance in an Owin based application maybe you want to update the security packages due to changes to the backends used for authentication, or if a security flaw is found.
It can also be useful if you are migrating to a new aspnetcore application using systemweb-adapters.
I don't know if you will be able to get any help from Microsoft on this, but I would suggest asking on some of the forums etc. to see if anyone has any insight. If you find a solution to the problem, please do come back to me and we can see if it can be built into the SDK for other webforms users.
julealgon
robrobrobrob
leusbj
OronDF343
After migrating our main WebForms projects to use this SDK, we noticed that the intellisense on aspx files (and any others such as ascx, etc) stopped working properly. Additionally, on each opened file, an error is indicated like this at the very first line:
asp:controls as well:I tried deleting the contents in the
%LocalAppData%\Microsoft\VisualStudio\[Version Number]\ComponentModelCachefolder and restarting Visual Studio. When I do that, intellisense starts working for a bit, but after a few seconds (not doing anything in VS, just time based apparently), intellisense just stops working again.To ensure this wasn't something particular to our project, I proceeded to create a brand new WebForms project using the standard VS template. I then performed the same conversion steps that we did on our real project on this minimal template, and I started observing the exact same behavior.
After the conversion, I attempted adding the
EnableWebFormsDefaultItemsmsbuild flag (which I was unaware of) as well as tried using different versions of the DotNetCompiler (when we migrated our own project, we used theExcludeSDKDefaultPackagesflag).Is this a known issue? How do I fix it?
For reference, here is a solution with 2 projects from the standard template: 1 converted, and the other standard.