I have just finished the development of a web service application in visual studio.
Is there an easy way to wrap it in an installer, so that I can just ship it off to technical support, and they can have a wizard based installer that will fully setup an IIS site for them, either in 6 or 7?
You can use Visual Studio's built in setup project. I've only tried this once on a test project, but it created all the necessary stuff in IIS 6 just fine.
I would suggest you export the IIS METABASE for your local instance of the service and then this can be imported into a new server to create the correct IIS configuration. Have a look at Copying IIS Configurations using iiscnfg.vbs The METABASE is just an XML file and you will easily see the specific values that allows you to edit them should the deployment be different in anyway.
Related
Any idea how to run ASP.NET 5 project in full IIS (not express) from within Visual Studio 2015 (via start debugging with F5 key)?
Atm I'm getting:
Couldn't determine an appropriate version of KRE to run.
I know it's not officially supported yet, but since IIS Express can do it, so should full IIS?!?
Let's say you created an ASP.NET 5 web application out of the template provided in VS 2015 Preview, then you can follow either of the approaches below:
Run the kpm pack command to create the deployable package with the appropriate options.
Example:
kpm pack --runtime KRE-CLR-x86.1.0.0-beta2-10690 --out "C:\MyWebApps\WebApplication1" --wwwroot-out wwwroot --configuration Release
Right click on the web application project and do a Publish to local file system directory.
Once the above step is done, in IIS, you can create a virtual directory application (or Website if you wish) to this deployable package's wwwroot folder. Example: "C:\MyWebApps\WebApplication1\wwwroot"
I just had a similar issue with beta4.
Note that the names have changed now so instead of a KRE it's now a DNX, although IIS was still showing the error calling it KRE despite this.
Anyway the solution for me was to:
right click the project in question in Solution Explorer
select "project name" Properties
tick Use Specific DNX version
tell it exactly which one you want to use, for me that was 1.0.0-beta4, .NET Core, x64
The project then ran in the browser for me.
I am new to the Visual Studio 2013 IDE / Environment...
I have inherited an older (ASP.NET) web site that is currently being maintained using Microsoft Expression Web 4 (which is no longer supported by Microsoft). The test and production web sites are hosted remotely using IIS 7.5
I have two questions with regard to migrating from Expression Web 4 to Visual Studio 2013:
Is there any way to simply copy (FTP/download) the web site from the production server into Visual Studio 2013? i.e.: create a new empty web site in VS 2013 and then copy everything from the production web site. Will this retain “sub-web” folders, etc.? (I doubt it).
When using Expression Web 4 to publish pages to IIS – some of the files in Expression Web are marked as “Exclude from Publishing” (because some files like web.config differ depending if publishing to the test or production server). I have not found anything in VS 2013 for an ASP.NET web site project that allows me to set individual files so they are excluded from being copied to a remote web site. Does such functionality even exist?
Any insights would be appreciated.
Thanks in advance.
For #1 if you have Web Site project open in VS (not to be confused with Web Application project), you can right-click on it and choose Copy Web Site. This will bring up an window where you can connect to a remote site (e.g. with FTP) and sync files back and forth.
(Note: this feature is ancient and nobody knows about it anymore)
For #2, it depends. In the case of web.config, you can create a publish profile (right-click the project and choose Publish) that will let you use web.config transforms to modify the web.config file for each publish destination. Once your publish profile exists, you can right-click on it in Solution Explorer and choose Add Config Transform, which will only apply when you publish to that destination.
For other files you wish to exclude, you can modify the .pubxml file for your publish profile as described here using <ExcludeFilesFromDeployment> and <ExcludeFoldersFromDeployment>. (The blog post talks of editing the project file, but that's no longer necessary since VS2012; use the .pubxml files instead.)
We have a SharePoint farm configured with one SQL server, an Application server and one Web Front End. All assemblies run from the GAC on the WFE, except one. This one dll has to be forced (using gacutil) into the GAC on the App server in order to see changes in our SharePoint application.
My question is, what determines that this dll must run on the App server and not with the rest on the WFE? I assume because of this, I cannot debug in Visual Studio from the WFE. Do I have to install Visual Studio on the App server as well?
When setting up a timer job, it's possible to use the constructor to specify a specific server. That's likely how things got set up for this solution and associated .dll file. More info on that here:
http://www.martinhatch.com/2009/08/sharepoint-timer-jobs-and-multiple.html
As for adding Visual Studio to servers on your farm, if this is your production farm I do not recommend doing this. If you really need to debug in production (you really, really should have a development box set up for this), do it via remote debugging.
I have just installed VS2012 and created a MVC project. I right clicked on project and selected property, I chose Web tab. I selected "Use Local IIS Web server" but the "Use IIS Express" checkbox is disabled.
I checked my C:\Program Files (x86)\IIS Express\ folder and IIS Express 8 is there.
Any particular reason?
If I fall back to use Visual Studio Development Server, I have 50% of the chance to see "Server Too Busy" message.
All you have to do is to activate IIS in your development machine:
Start -> Control Panel -> Enable or disable Windows features -> Internet Services
Then check mark in World Wide Web Services -> Common HTTP Features
And check mark in World Wide Web Services -> Application development Features
That's all you need.
Using Full IIS has some benefits. One is that it is always running, so you don't have to start your VStudio Project to unit test. Another is that you can create an actual site and configure IIS mirroring production, using the same Admin Tools, which makes it easier to support when deployed in an environment. And, I seem to recall that IISExpress had issues with Application Routing. On the flip side, I don't see an issue with using the Full IIS. Granted, IISExpress is much better than Cassini, but if there is no reason to not use Full IIS then I conitnue to advocate it's use.
sorry for possibly a very stupid question.
I have one of those Visual studio Web Sites ( ie not a web application) ,
is there any way I can automate the creation of the IIS Web Application that points to the web site within Visual Studio ( ie then when developers open the solution, the IIS site will be set up automagically?
Sorry, just not famiiar with the Web Site side of things
Thanks
AFAIK It's not someting Visual Studio will do out of the box. What you could do is create a batch file that creates the virtual directory then opens the solution. Store it in source control and your developers will be able to run it instead of opening the solution directly.
There are a few options for creating an IIS virtual directory automatically - see this and this.
Also - if you are using VS2005 or above you could change you application to use the development web server instead of IIS and then you won't need to mess around with virtual directories at all. Select 'Use default Web server' on the 'Start Options' section of the projects property pages.