I have created a web application using Visualstudio 2008 using C# on my computer.
I am using windows server 2003.
I have now published the webapplication and put those contents in the server.. with a field called inetpub\wwwroot.
i have created a root directory for it in the IIS with the name "super".
Now i need to see this in internetexplorer how do i do this...
I am new to this so please help me..
Thanks
Is there a Procedure on how to do all this from the start...
If you have created a .net website or .net web application, you can follow these instructions on Deploying ASP.NET Applications in IIS 6.0. In overview, when you do a publish from visual studio, you're compiling the application down to it's assemblies, you're stripping out the code behind files, and only moving over what is needed to run the site/application. Your webserver should be setup with a virtual directory pointing to the published folder, and it would be a good idea to have a Default.aspx page in the folder since the webserver looks for this page as it's starting point. Usually the default website is the site used inside of IIS for websites (at least when you've only got one). You should be able to right click on a file and browse the file if you have followed all of the setup instructions found in the referenced link.
Good luck, and hope this helps.
Within IIS, you could right click on default.asp and select browse.
Related
I got an ASP.NET project. I'm going to send the project to a server company where they will host it. How do I prepare it to be hosted? I assume I cant simply send the whole project to them. What are the steps to prepare the project to be readable in their server?
This is my first project, never done it before.
Used Visual Studio 2015, WebForm/ASP.NET.
It's going to be hosted via a server company, no clue about anything about their servers.
Also got a MS Access database in App_Data folder within the project.
PS: I found "Publish" by right-clicking the project in Visual Studio's 'Solution Explorer'. I've been checking out this link but it's really confusing.
Any help would be greatly appreciated.
When you publish an application, most of the time it will run just as it does when you debug it, but on the server. All the binaries are copied there, with the Web.config, and most like all you have in your application, but the source code will not be avaiable of course. You don't need to send the application to the company which will host your application, most likely they will give you the server address where your application will be published, they will create an account for you, with some permissions, and credentials. And of course, you can read more about IIS server, it will be pretty relevant to you, and you can configure yourself a server where you can publish your application, just to see how it works.
Set up your own application on your own IIS and experiment locally until you have all stuff in place. Then copy to you hosting environment.
Later on you can script this process to have full control over what you need in dev and prod respectively.
I'm working on a Visual Studio 2012 web application, and need to allow colleagues to view the current website by my IP address (while I would access it my localhost). It appears that hosting the site locally through IIS7 and allowing others to access it by my local IP the simplest method. After troubleshooting and experimenting for a day though, I still don't understand the relationship between an IIS7 site/website/application and Visual Studio web application, and the MSDN explanations are really hard to follow.
Basically, I'm trying to understand:
1) How to set up a IIS website and application (should the 'physical path' be the VS solution folder or deployment package .zip folder?, for example)
2) How to most simply deploy the web application (e.g. File System/ Web Deploy/ Web Package, etc.) and
3) The order to do all of this.
I'm running VS as administrator, my port 80 is open, and have IIS7 set to use .NET v4, yet when I publish the selection using File System in VS2012 to my C drive, the resulting site gets a HTTP:500 error, with no source code underneath. (Also, before even publishing, setting the solution to use my Local IIS instead of IIS Express and previewing results in a blank page). If there is a better way to do this please let me know.
Thanks in advance.
If you don't want to learn (or bother) with the details of setting it up, you can use a small utility like 'ngrok' that will allow others to view your website at 'localhost'.
Takes about 5 minutes to learn and get up and running (and its free).
https://ngrok.com/
i can not reload the WebApplication project, i got this message error
i moved the server to another place, so the IP is changed.
i already change the ip on IIS and WebApp config
i already uninstall IIS and reinstall
i already use aspnet_reggis -i
but still i, can not reload the WebApplication.
thanks you in advance
PS: i m sure is because the IP configuration. it work well at my home, now i bring the computer to office...it not work anymore....nothing change just the IP my home is not the same like IP in my office
the error message says: the project web ESPTEMPS_WebApp is configured for IIS, the website is not found.
You most likely need to configure your IIS for your website.
here's a helpful link to do this: http://msdn.microsoft.com/en-us/library/cek8kw6e.aspx
Good luck,
Your application is configured to work with IIS, in your case, IIS is not installed in your system or maybe the developer used IIS Express when developing. (You need to install VS 2010 sp1 to get IIS Express 7.5 integration with VS)
What you can do is:
Close your solution and open the csproj file in notepad (of the project that is giving problems)
Find and set these values:
<UseIIS>False</UseIIS>
<UseIISExpress>False</UseIISExpress>
Then reopen your solution again with visual studio. You will be able to debug with the web developer web server.
I found a very good reference for you. It will walk your through set of steps to help you configure your IIS. Here is the link. Please ignore the steps that are not applicable to you. But basic idea is:
Open Project Properties and go to Web tab
Select local IIS web server. If it is already selected, it will show you a virtual directory. If it doesn't already show selected, then mention the virtual directory.
I've spent a great long while googling this problem without any luck and I've always found great answers here, so here it goes:
[BACKGROUND]
I have a web application which was developed in C# with Visual Studio 2008. It was a part of a solution with another project which contained a web service. This was not created "IN" IIS (I was using the Cassini ASP.NET Development Server at first, but have encountered numerous issues). I finally got approval to install IIS 5.1 (Government Network - using Windows XP) so I wanted to host my apps there for development.
I moved my projects to another folder created my IIS virtual directories, pointed them at the right location, updated my security settings, ensured that .NET 2.0 was selected and tested the site and web service. They function perfectly in IIS.
[ACTUAL PROBLEM]
I open Visual Studio, click File > Open > Web Site > Local IIS > [Application Name] and it opens up, but my .design files aren't nested under the ASPX / ASCX objects, and when I right click on it and select "View Code" it takes me to the markup instead of the code behind. Once I reach the code behind, I don't have access to any of the members of the design, as though there was a problem with the wire up.
I have tried creating a web site from IIS through Visual Studio, and it works perfectly. I closed it and opened it up again to see if that functionality would persist and it did.
I've encountered this before and have had to re-create a new site through Visual Studio, and manually re-populate it with all of my classes from a "broken" solution. I would love to solve this the correct way.
Please help!
Adam
The best thing I could suggest would be to go through the Project files with a fine toothcomb (as Filburt suggested) and make sure the references are pointing to a virutal directory (or via the inetpub folder, if thats how your IIS settings are configured), rather than a file system directory.
You might also want to check your IIS settings. Is your virutal directory set up to point to a file directory?
Good luck!
All dependencies between markup, .design and code-behind files are laid out in the project file.
You could use a sample project to discover how to correct your existing project.
I have recently inherited an ASP.NET website to look after.
I have a copy of all the files but coming from a PHP background I am not sure how to make changes and deploy it.
After I make changes to the site I presume I need to compile it. But can I then simply copy the site onto the server or do I need to create a setup package and 'install' it over the top of the production system?
Also, where does the code-behind DLL 'sit' in the file system?
Is there a decent guide to this kind of stuff?
After making changes and testing them with your local copy (I'm assuming you know how to do that), click the "Copy Web Site" button at the top of the solution explorer. This lets you connect to a remote server (your production box, presumably) and will compare your local version of the web site to the one on the server, and flag any files that have been changed locally. You can then update the server version so that it matches your local version.
If you're deploying the web app as a compiled DLL (instead of as uncompiled CS files), the DLL should sit in the application's \bin folder. Even with a compiled DLL, you still need to deploy the ASPX files.
You don't have to go for a setup. The answers to your questions differ based on whether you are using a 'WebSite' or a 'Web Application Project'. Please answer to following and we can follow up after that;
Which version of .Net / ASP.Net you use? (1.1, 2.0 or newer)
When you open up the package in VS (Visual Studio) and right click on the top most group (solution explorer) do you see options like Build web Site, Publish Web Site?
As a long-shot just try to create an IIS web site pointed to the root of your files and see if anything comes up. If this works the work process will be;
1. Do a change
2. Compile
3. Hit the web site URL and see whether it reflects