VS2010 doesnt generates app pool name parameter for msdeploy package - visual-studio-2010

I'm using VisualStudio 2010 to generate web deploy package for web application.
I have enabled "Include application pool options" in publish settings.
So after building web package on my Windows 7 PC from VS 2010 I get web package with all additional files, and in .SetParameters.xml file there is "IIS Web Application Pool Name" parameter to specify app pool name when deploying package. In package archive.xml file has app pool configurations.
The problem is with Server 2008 R2 build server - when I'm building web package from VS 2010 there is no "IIS Web Application Pool Name" parameter in .SetParameters.xml file but package's archive.xml file has app pool configurations and while deploying web package app pools are created with default names.
The question is -
How it can be that app pool configuration is in package but there is no "IIS Web Application Pool Name" parameter?
Maybe there is something with Msdeploy installation or VS2010 installation on server?
How I can declare this parameter in VS2010?

I have finally solved this issue.
The problem was with Visual Studio installation - on my development Pc is installed VS 2010 SP1, on other Pc was installed VS2010.
After I've installed VS 2010 SP1 update on other Pc, package was generated correctly and with "IIS Web Application Pool Name" parameter in SetParameters file.

Related

Is it possible to debug a .NET application that is deployed to IIS on my local machine?

I have incorporated Azure authentication in to a .NET application on my local development machine. When I debug/run the application in Visual Studio the app runs just fine.
I have deployed the application to IIS on my local development machine and have configured a new site binding of type HTTPS which uses an SSL certificate that I have created locally and added to my "Trusted Root Certification Authorities" store. When I try to browse the application through IIS, I get a generic error message that is generated by the Application_Error method in my global.asax.cs file.
Is it possible for me to use a debugger to "step through" code that has been actually deployed in IIS? I think that I have found MSDN documentation that describes doing this for a .NET Core application (https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/development-time-iis-support?view=aspnetcore-2.1) but I my app is written in .NET 4.8 so I don't think it applies for me.
To debug an ASP.NET application that has been deployed to IIS, install and run the remote tools on the computer where you deployed your app, and then attach to your running app from Visual Studio.
For more information about "Remote Debug ASP.NET on a Remote IIS Computer", you can refer to this link.

Visual Studio 2012 'Publish Profile' to Windows Server 2008 - 'Destination not compatible' error

I am deploying a website form Visual studio 2012 to a Windows Web Server 2008 R2.
I can connect to Web Deploy fine - though I get this error:
1>(27/05/2013 21:03:29) An error occurred when the request was processed on the remote computer.
1>Source (appHostConfig=Default Web Site/myAppMVC4) and destination (appHostConfig=myapp.com) are not compatible for the given operation.
1>Publish failed to deploy.
I fixed this by right clicking the project (not solution) - clicking Package/Publish Web and deselecting 'Include IIS settings as configured in IIS'
Now works fine.
Maybe this is because I'm using IIS 8 on Windows 8 locally - and IIS 7 on Windows Server 2008?

What needs to be installed in a Windows Server 2008 R2 to allow it to run ASPNET MVC 4 apps?

I've installed the .NET 4.5 framework using the dotNetFx45_Full_x86_x64.exe installer, and the ASPNET MVC4 framework using the AspNetMVC4Setup.exe installer in a Windows 2008 R2 server, yet I keep getting the message 'There is no build provider registered for the extension '.cshtml'.' while trying to run my ASPNET MVC4 app.
I've fixed this temporarily by adding a buildProviders section in my Web.config, but I would like to know how to setup a server so that I can use the current framework without having to touch my Web.config (the same way I can run them in my dev machine).
This is a shot in the dark, but "aspnet_regiis -i" maybe?
(make sure to run the version in the correct directory on your server)
http://msdn.microsoft.com/en-us/library/k6h9cz8h(v=vs.80).aspx
UPDATE:
Did you also deploy the following .dlls in your BIN folder of your web app?
System.Web.Helpers.dll
System.Web.Mvc.dll
System.Web.WebPages.Deployment.dll
system.Web.WebPages.dll
System.Web.WebPages.Razor.dll

Enable 32-bit applications in IIS 7 using VS2010 deployment capabilities

I want to deploy the WCF service (.net 4.0) to IIS 7 and use the built in deployment capabilities of Visual Studio 2010 for this. There is a good article about that on msdn http://msdn.microsoft.com/en-us/library/dd465323.aspx but there is still one unclear thing for me.
I want to set "enable 32 bit applications" app pool setting during deployment and it seems like there is a special option to do this in Package/Publish Web section of visual studio project. There are two checkboxes there, namely: "Include all IIS settings as configured in IIS" and "Include application pool settings used by this Web project". But when I select them, build a deployment package and deploy it to IIS on different computer then "enable 32 bit applications" is not set in the target environment (WCF service itself is installed successfully and working).
Probably I'm missing something or misunderstood the intention of IIS settings inside the VS2010 project. Any comments are welcome.

Visual Studio 2010 published web site returns "Could not load assembly App_Web_xxxxxx.dll"

I am working on client's application in which we have two servers - development server and testing server. We first develop applications on development server and then publish it and host it on test server for client testing.
Testing server has Microsoft .NET framework 3.5 SP1. On development we have Visual Studio 2010.
We publish the website on development server using VS 2010 and then copy that folder to testing server and host it on its IIS.
Whenever we try access any aspx page of site hosted on testing server, we get error:
Could not load assembly App_Web_xxxxxx.dll". Make sure it is compiled before accessing the page
What can I do to resolve this?
This could be due to a lot of reasons.
I would start by trying one of the following things..
Make sure your IIS Site has the correct .net version specified - same as your application
Make sure you have all the required .net components installed in windows features (control panetl)
Look at event viewer for more errors and post it here
OK guys here is the solution.
Since my testing server is having Microsoft .NET framework 3.5 so on the development server while publishing from VS 2010, I have to choose target framework as 3.5.
Do this:
Right click web site -> Property Page -> Build -> Change the target framework.
After doing this setting, publish the web site again.

Resources