I'm not sure this is possible from the docs, but can you remote debug an vagrant ASP.NET webforms site using omnisharp remote debugger? I can't find much info on this anywhere
EDIT:
Trying to setup omnisharp for VScode
https://github.com/OmniSharp/omnisharp-vscode/wiki/Attaching-to-remote-processes
I'm using this vagrant setup
https://github.com/dmitry-zaets/vagrantfile-windows-iis-mssql/blob/master/Vagrantfile
I also added ASP.Net to this box
DISM /online /enable-feature /featurename:IIS-ISAPIFilter
DISM /online /enable-feature /featurename:IIS-ISAPIExtensions
DISM /online /enable-feature /featurename:IIS-NetFxExtensibility
DISM /online /enable-feature /featurename:IIS-ASPNET
I am running aspnet_regiis.exe file from command prompt but it is giving the following error.
Need your help!
Did you try going to http://go.microsoft.com/fwlink/?linkid=216771? It gives step by step instructions on how to install hook up .NET framework in IIS.
I am trying to learn how to deploy my first website which is physically located here (C:\Users\Amal\Documents\Visual Studio 2008\WebSites\ErrorHandlingTest). I am using instructions from some book. after installing the Internet Information Services on my laptop which has Windows 7 ultimate on it. I added a virtual directory and gave it the alias (MyFirstWebsite). after that I was able to open the website just by typing
http://localhost/myfirstwebsite/mypage.aspx
on the address bar of my firefox v.21 browser.
the book then told me to do some code compilation to the website by using the command-line tool named aspnet_compiler.exe which is supposed to compile my website into binary files after running this command :
aspnet_compiler -m W3SVC/1/ROOT/MyFirstWebsite C:\MyFirstWebsiteDeply
but I got this error:
error 1002: 'W3SVC/1/ROOT/MyFirstWebsite' is not a well formed IIS metabase path.
I use asp.net 3.5 , visual studio 2008 , internet information services version 7.5.7600.16385
Try
aspnet_compiler -m LM/W3SVC/1/ROOT/MyFirstWebsite -f C:\MyFirstWebsiteDeply
You had missed the "LM" at the start of the metabase path.
Actually the iispath should be /LM/W3SVC/1/ROOT/XXX.
Pay attention to the '/' at the beginning.
I am trying to encrypt some sections of the web.config file of one of my applications by using RSA encryption at user level.
So I followed all the steps listed in here and I succesfully created the provider and granted access to my application. However, I have some problems in specifying the virtual path for my application.
I run IIS 7.5 in a Windows Server 2008 R2. My application is called www.testsite.com and its ID is 4.
The aspnet_regiis tool is placed in the Windows\Microsoft.NET\Framework\[version] folder:
Therefore in order to encrypt the connectionStrings section I run the command:
aspnet_regiis -pe connectionStrings -app "[Application Path]" -prov "myRSAProvider"
I tried as [Application Path], the followings:
/W3SVC/4
/W3SVC/4/root
/W3SVC/4/root/www.testsite.com
/www.testsite.com
And I always receive the error
The configuration for virtual path '[Application Path]' and site
'Default Web Site' cannot be opened.
Failed to map the path '[Application Path]'. Failed!
I tried to browse many resources on the web but this IIS virtual path specification is not extensively covered. In IIS6 I could get it by running aspet_regiis -lk but this command does not work anymore in IIS 7.5. May somebody help?
You may be having two issues.
At the end of your command statement specify your site with the command -site "4" Also note that instead of the #4 you could write in your site name instead. e.g. -site "www.testsite.com"
aspnet_regiis -pe connectionStrings -app "[Application Path]" -prov "myRSAProvider" -site "4"
It is also very important that you run the command prompt as Administrator.
I had the same error you had running IIS 7.5 in a Windows Server 2008 R2 and this is what helped me.
Using IIS7.5, the website works fine in Visual Studio but when I try to deploy on IIS get the following error.
Module IIS Web Core
Notification ExecuteRequestHandler
Handler PageHandlerFactory-Integrated
Error Code 0x8007000d
Requested URL http://localhost:80/EFT/default.aspx
Physical Path
C:\inetpub\wwwroot\EFT_Converter\default.aspx
Logon Method
Anonymous
Logon User
The version of .Net you are using has not been registered with IIS correctly.
If it is .Net version 4 on a 64-bit 2008 server use these two commands to fix it.
%windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i
%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -i
Open command prompt on window and run:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\ aspnet_regiis.exe -i
This will resolve your issue.
Where your handlers are defined in the web.config, add a <clear /> before the first item in the list, if there is not one there already. Also make sure that the application pool running the web site is running the version of .Net that you are targeting in your code.
Try to set web config in this way:
<system.webServer>
<validation validateIntegratedModeConfiguration="false" />
</system.webServer>
Ensure you have ASP.NET has been installed correctly. You should see default application pool named "ASP.NET 4" or something like this. If it's not looks like ASP.NET not installed correctly. Try aspnet_regiis -i in .NET 4 CMD.
Please go through this post.
From the post:
Click Start -> All Programs -> Accessories -> Run
In the Open textbox paste in the following line (see list of all .NET Framework version install, repair and unistall command lines here):
For silent repair on 32 bit computer with .Net Framework version 4.0.30319 use:
%windir%\Microsoft.NET\Framework\v4.0.30319\SetupCache\Client\setup.exe /repair /x86 /x64 /ia64 /parameterfolder Client /q /norestart
For silent repair on 64 bit computer with .Net Framework version 4.0.30319 use:
%windir%\Microsoft.NET\Framework64\v4.0.30319\SetupCache\Client\setup.exe /repair /x86 /x64 /ia64 /parameterfolder Client /q /norestart
2. Click OK to start the repair.
3. After, the repair ran for a few minutes, I restarted IIS 7.5, and things began to work correctly!
I had this problem and found that removing the following folder helped, even with the non-Express edition.Express:
C:\Users\<user>\Documents\IISExpress