We have a big solution that we just recently migrated to Visual Studio 2012. In this solution, one project is the main Web Application in IIS and the other projects are folders inside this Web Application. Every time we open the solution, VS2012 turns these folders into Web Applications and it breaks the site. Is there any way to avoid this conversion?
We found the solution. We changed the projects properties to not use IIS but a Custom Server with our local url.
Related
I have a Web API project and an authentication project built on .NET Core and I set up several startups in Visual Studio to run the project when starting IIS. What to try to figure out is if there is any way to do this programming and not from visual studio. My idea is when running the API, somehow refer to another project (in my case the authentication server) at the API startup or elsewhere and this one runs both projects (as happens when setting up multiple startups in Visual Studio).
From another question, got to know that there are three development models in Asp.Net. I have installed VS 2012 in my laptop, but when I try for new web project, I am not able to see the WebPages project template.
Do I need to download the template or Am i doing it in wrong way?
In Asp.net/WebPages, it has a WebMatrix downloadable link. Does that mean, Asp.net webpage project can be created only with WebMatrix?
Web Pages projects are Web Site Projects, so you create them by choosing File ยป New Web Site, then choose ASP.NET Web Site (Razor v2).
I want to know if it is possible to develop web parts without installing sharepoint?
I choose Visual Web Part then I get sharepoint not installed error.
You can't develop it without SharePoint on same machine.
The answer is "Yes", you can. But if you do that then you loose all features of Visual Studio for development for SharePoint. You will need to create proper visual web part project artifact structure manually which could be tricky. Also you will have to create wsp package manually or using tools like wsp builder. Then you can copy this wsp package to sharepoint server and deploy it.
This might be a stupid question, but I have a problem with Visual Studio 2013 and IIS (not Express), that the Visual Studio debugger by default uses IIS Express (iisexpress.exe) to debug code. But I do not want that, but I want to use IIS installed on my computer (w3wp.exe).
I succeeded in debugging with IIS by using Attach to Process... and then selecting All Users and then picking w3wp.exe as a process. But I need to do this every time I start debugging. Is there a way to use IIS by default? In Visual Studio 2012, everything worked well, but in VS 2013 I cannot find an option to use IIS (w3wp.exe) by default.
I am debugging a Web Site ASP.NET 4.0.
Thanks for any help!
If your website project was opened via IIS, it should debug the IIS process automatically. If your site exists in IIS currently, you should be able to find it via File -> Open -> Web Site.
If you opened an IIS Express based website project (or via the file system, which uses IIS Express by default), then run the site through IIS, VS doesn't know that the site is running in IIS.
In order to get this working on my setup (VS2013, IIS7, Win7) I needed to go into IIS Management Console and manually enable Windows Authentication.
In Visual Studio 2012 there is no website deployment, ok I switched to Web Project, now it has generated tons of page.designer.cs files, how can I make a web app project without the designer.cs files ?
Visual Studio create these files for easiness of coder, you will always get these kind of files when you create a new web app project. These files creates the necessary code you need for designing the web page.
But once you publish the web app to the server using the VS2010 publisher, these files are gone and only the .aspx files are remained. Why does this happen? because your code i.e. .cs files needs to compiled before it can be published on the server.