In Visual Studio, is it necessary to convert a website into Web Application project for Web Deploy to work?
It's not possible to publish a website created in Visual Studio 2010 unless it's a Web Application project.
File based web projects created using File -> New -> Web Site... or Shift+Alt+N (assuming you haven't changed the keystrokes) can only be published using FrontPage extensions when publishing to http://www.mysite.com.
So yes, you need to convert your "web site" project to a "Web Project" to be able to publish using Web Deploy.
Related
I am creating a Web Setup Project using Visual Studio 2013 to create a MSI installer for an ASP.NET Web API project. I am using this extension from Microsoft that brings these projects into VS2013.
I am trying to understand what the Web Setup Project does in relation to IIS. It appears there is no difference between a Web Setup Project and the standard Windows Setup Project in what it actually does. They both install the files to a directory that I choose during installation. I would expect the Web Setup Project to create a site/virtual directory in IIS but it's not. It doesn't do anything different than if I use a windows Setup Project.
Is there something else I need to do to make the Web Setup Project install a site/virtual directory to IIS? Or is the correct behavior to just install the files to a directory and that's it?
There is no documentation for the VS2013 version of this but I am looking at the reference here for VS2010 and the product appears about the same
I'm using SharePoint 2010 and I have developed webparts at visual studio 2010. I'm already using WSP to deploy my web application into server, but still should create and add the webpart manually through SharePoint site. Is there any way that we can deploy the application and automatically create and add all webparts into the site?
Generally web parts are added to pages using features. Basically you create one site collection feature to deploy web part files to web part gallery and web scope feature which adds this web parts to pages (for example default site page).
I have one project which has APP_CODE folder and runs with Windows Authentication.
1) I created Web Site and added the files of project but I couldn't run with windows authentication
2) Then I created web application project and check "Use Visual Studio Development Server". But now, I couldn't get access to the classes which are in App_Code folder.
There is no choice to select Visual Studio Development Server when I use Web Site project!
Questions:
Why can't I add APP_CODE folder to the Web Application ?
Why can't I run my Web Application on Visual Studio Development Server?
In which circumstances I should choose Web Site or Web Application options ?
PS: I want to put pictures of Web Application and Web Site:
Web Application:
Web Site:
Anybody know where the VS 2010 One-Click Web Publishing settings are stored?
It would be awesome it a team could share the settings so a quick deployment to a test system is always a button click away.
It's stored in the same project directory as the project you've deployed, stored as an XML file. Look for a *.Publish.xml
I have developed an ASP.NET web application in visual studio 2008. I want to run the same application on another system, but Visual Studio is not installed on that system. Is there a way I can run without visual studio?
I heard about deploying, but I don't know much about it.
You can publish your site from Visual Studio to a server that's running IIS, more info here:
How to: Publish Web Application Projects
You can use the built-in deployment features of Visual Studio (right click on the web project, select publish and follow the prompts) or you can simply copy all the dlls plus your content files from the web project to the IIS folder you want to deploy to (known as xcopy deployment). You could also deploy via a setup project, which will create an MSI package, but that's a bit more work. Here's a couple of links that might help, but you can do a search for the options described above and you will find plenty of resources:
Deploying ASP.NET Applications - Part 1
Deploying ASP.NET Applications - Part 2