Last post Aug 28, 2014 11:41 AM by PatriceSc
Aug 28, 2014 05:42 AM|Chris17|LINK
I built an MVC 5 app that is to run offline on IIS.
I have never deployed to local IIS before.
Please how can i deploy this app to my clients PC and i think IIS needs to be upgraded, how can i do that too?
Aug 28, 2014 06:03 AM|PatriceSc|LINK
My understanding is that you'll deploy this app on each and every user machine on a local IIS? (plus you don't need a DB?)?
I would forget about it. You basically loose all the interest of a web app. I would rather consider another approach (not sure what you are trying to do, just a Windows app maybe ?)
Aug 28, 2014 07:16 AM|Chris17|LINK
Did not really get you Patrice, I just have a web app with a database and was built with VS. Its MVC5 app. I do not want to use VS's web deploy because i will have to install VS in my clients's computer. That's all.
Aug 28, 2014 08:16 AM|PatriceSc|LINK
I meant that usually a web app is installed on a single web server and used from all client computers using a web browser pointing to this single website. Here it seems you want to deploy a separate web site on each and every client computer (how many?)
which is really unusual (at least this is my understanding for now). Not sure what is the reason for doing so? Double check this is really what you need.
Regarding MVC5, AFAIK it depends on ASP.NET 4.5. So technically speaking IIS7 or later which is the minimal version installed on an OS that does support .NET 4.5 should be enough.
Aug 28, 2014 09:30 AM|Chris17|LINK
Ok. I am installing on just one PC.
On the other hand if i need to install on PC (Server) and access from different PCs(Clients), how do I?
Aug 28, 2014 11:41 AM|PatriceSc|LINK
So you'll use a web server inside your company? You don't have an admin people that could help?
- you'll create a web site on the web server:
- you'll publish your application files to the location of this web file (using just a file system publish might be easier for a start)
Likely you (or the person in charge) will create a DNS name so that yoursite.company.com "points" to this web server (and the site is selected by using the same "host header name" you'll find in the IIS web site creation steps)
At this point if someone points his browser to
http://yoursite.company.com it will show the default location for you site...
Web Deploy could also help (but needs first to be configured) and is unrelated to VS (ie. you can install web deploy to a web server to ease deployment, you don't need at all to install VS).