Now that MVC 3 Tools Update has been released, that's all I see on the Web Platform Installer -- I no longer see MVC 3? Is this because the Tools Update is essentially MVC 3 PLUS enhancements to the development environment? Presumably, none of these additions are needed on a server so I thought that MVC 3 would still be offered for server installs.
So can/should I install the MVC 3 "Tools Update" from the Web Platform installer on a server?
I know this doesn't help you Decker, but it may help others:
The easiest way to get MVC on the server is by using the "Add Deployable Dependancies..." menu:
Also useful for deploying SQL CE.
You can use the installer from WebPI on the server just fine. It will detect if you don't have Visual Studio installed and will only install the runtime.
You could also try unzipping the installer file and only copying the runtime MSIs but I think that's overkill.
You could also use Web Platform Installer from the command line:
webpicmd /install /Products:MVC3Runtime /log:webpi.log /accepteula /SuppressReboot
If your servers don't have internet access, you can use the offline flag from a machine which does have access to download a copy of the required install files.
So your flow would be as follows:
Prepare Cached Version of Installers
webpicmd /Offline /Products:MVC3Runtime /log:webpi.log /Path:"%~dp0wbpiCache"
Install from cache (copy folder structure to target machine)
webpicmd /install /Products:MVC3Runtime /log:webpi.log /accepteula /SuppressReboot /XML:"%~dp0wbpiCache"
You don't need to install MVC3 on a server.
Just copy the MVC DLLs along with your projects.
Related
In previous versions of .Net, there were some different methods of creating a project that could run as a console app or be installed as a service.
Things like TopShelf or other approaches like: .NET console application as Windows service
This is a nice convenience for development and later deployment. I put together a vNext console app using a similar approach to the accepted answer here: .NET console application as Windows service.
The issue is that vNext runs things in a different way. If you create output, it no longer gives you an exe to install. Instead you get a nuget package and a .cmd file that will tell dnx to host your application. The command file looks like:
dnx --appbase "$(dirname $0)" Microsoft.Framework.ApplicationHost My.vNext.Service $#
So my question is: Is there a way to install this thing as a Windows service given the new console application approach?
We have a .net MVC application where it involves deployments every week. We need to package the application and give it to the clients every week for them to install as an .exe or .msi
The package will involve DB changes also and site in IIS is already set.
The exe/msi just has to replace the old files(bin and views) and do the DB changes(run scripts). I don't want client to see either our code or DB script while installing.
So how can I achieve this as a single package?
I have one TFS 2012 environment with Update 1 and today I updated this environment to Update 2, the installation is completed with sucess, but my portal web access is not working and is returning the bellow error
Could not load file or assembly 'System.Web.WebPages.Deployment, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
Before the update, my environment was running smoothly but now after the installationd Updete 2 is not working
This error is about ASP NET MVC, all right?
Can you help me?
I did not installed update 2 yet myself but did you check your administration console? And check also your event viewer, maybe you'll find interesting information/errors there that can help you out.
I've installed update 2 but haven't encountered the issue you have. I did have some issues and ended up turning off the application pools for the Portal and disabling TFS on the server by using the TFSServiceControl quiesce command before installing the update.
One thing I have noticed is that TFS Update 2 installs a .Net 4.0 version of 'System.Web.WebPages.Deployment' into the GAC an the location:
C:\Windows\Microsoft.NET\assembly\GAC_MSIL\System.Web.WebPages.Deployment\v4.0_2.0.0.0__31bf3856ad364e35
Assuming you are running x64 there is a .Net 2.0 version of this assembly in
C:\Program Files (x86)\Microsoft ASP.NET\ASP.NET Web Pages\v2.0\Assemblies
Alternatively for x32 it should be in
C:\Program Files\Microsoft ASP.NET\ASP.NET Web Pages\v2.0\Assemblies
I would suggest copying the .Net 2.0 version of this DLL from this location to the TFS Portal's bin folder and seeing if this resolves the issue.
This looks like a classic hunt and peck from the old days. I have no idea what types of installations this affects, but mine was a 2008 x64. Basically, I went to the web.config of the team (program files, long path, 11.0, web...\bin) and enabled error reporting.
Then I loaded it with IE in localhost addressing to get to the team project. Basically, it's looking for a bunch of .NET 2.0 DLLs. Copy each one it is looking for (find them doing a dir /s off the root, there are a few) to the local bin folder.
Thought these days had passed. Hope this helps someone.
I had exactly the same problem after upgrading TFS2012 RTM to update 4.
I was able to resolve the problem by amending the user of the Application Pool to a TFS Administrator user (it was set as Network Service I think).
I need to use CS Staging API to do some tests with a remote server.
However, the Staging option is grayed out for me and my colleague, at least
when i try to install the MSDN version (both Enterprise and Developer).
Any idea how can I at least use the Staging API with the remote server?
(I do not care whether I've got a local server or not)
Thanks in advance
Greg
You are trying to install on an unsupported OS
You cannot officially install CSS on the following OS':
Windows XP
Windows 7
Windows Vista
Having said this, the Greg has got CSS working on Windows 7 by manually copying the binaries (see comments below). Obviously, this is not supported or endorsed by Microsoft.
You are missing CSS pre-requisite software
For example, classic ASP is one of the pre-requisites. Make sure you follow
the (long) instructions in the CS 2007 Install Guide, you should be OK. You can also review a list of components CSS depends upon.
I am trying to precompile and deploy my ASP.NET MVC application from Visual Studio 2008 to a server running Mono 2.4 using a Visual Studio 2008 Web Deployment Project. Whenever I go to the website, however, I get an error message:
This is a marker file generated by the
precompilation tool, and should not be
deleted!
Has anyone got this working? Is there a better way to precompile and deploy an MVC application from Visual Studio 2008 to Mono?
You need to make sure that when you used the aspnet_compiler command, you specified the virtual directory where the applications would reside with the -v command. For instance, if you want to build and serve a stock ASP.NET MVC application, Mvc1, from localhost/Mvc1, you would need to make sure you use the -v /Mvc1 switch:
aspnet_compiler -f -p c:\projects\Mvc1 -v /Mvc1 c:\test\output
Since this is an ASP.NET MVC application, I would also suggest making sure you explicitly configured Apache mod_mono, rather than depending on AutoHosting. I discussed why in my answer to "Mono 2.4, AutoHosting and MVC".
You can now use the Apache mod_mono configuration tool hosted on the mono website.