ASP.NET

RichardGrimmer11-Apr-12 21:23

RichardGrimmer

11-Apr-12 21:23

Have to ask - since you've replied and been upvoted I have to assume you're correct, but I really can't see the logic for how you've arrived at that point - could you walk me through it - interested since I thought it was something different, and keen to improve!

C# has already designed away most of the tedium of C++.

jkirkerx12-Apr-12 6:47

12-Apr-12 6:47

"C:\Support.csproj : error : The Web Application Project Support is configured to use IIS. The Web server 'http://localhost:8080/support' could not be found.

In hindsight, I may change my answer, how about opening the Support.csproj file in notepad and posting the contents of it, it's just an XML file, but I want to see what it says.

I suspect that the project was programmed to use IIS Server for F5 RUN, instead of the webdev debugger, and your confused thinking that you have to install IIS Server in order to work on the program. There may be lots of customization to the project in that file.

I do both, I use IIS Server for testing in multiple browsers for compatibility, but I use the webdev for F5 RUN, for debugging.

dcof12-Apr-12 9:42

12-Apr-12 9:42

The following is support C# project type file listed below, If you want me to post more code from this web application, let me know.

<pre lang="xml">

<ProjectExtensions>
<VisualStudio>
<FlavorProperties GUID="{349c5851-65df-11da-9384-00065b846f21}">
<WebProjectProperties>
<UseIIS>True</UseIIS>
<AutoAssignPort>False</AutoAssignPort>
<DevelopmentServerPort>3358</DevelopmentServerPort>
<DevelopmentServerVPath>/SUPPORT</DevelopmentServerVPath>
<IISUrl>http://localhost:8080/support</IISUrl>
<NTLMAuthentication>False</NTLMAuthentication>
<UseCustomServer>False</UseCustomServer>
<CustomServerUrl>
</CustomServerUrl>
<SaveServerSettingsInUserFile>False</SaveServerSettingsInUserFile>
</WebProjectProperties>
</FlavorProperties>
</VisualStudio>

support.csproj user file listed below

<?xml version="1.0" encoding="utf-8"?>
<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<ProjectExtensions>
<VisualStudio>
<FlavorProperties GUID="{349c5851-65df-11da-9384-00065b846f21}">
<WebProjectProperties>
<StartPageUrl>PortalHome.aspx</StartPageUrl>
<StartAction>SpecificPage</StartAction>
<AspNetDebugging>True</AspNetDebugging>
<SilverlightDebugging>False</SilverlightDebugging>
<NativeDebugging>False</NativeDebugging>
<SQLDebugging>False</SQLDebugging>
<ExternalProgram>
</ExternalProgram>
<StartExternalURL>
</StartExternalURL>
<StartCmdLineArguments>
</StartCmdLineArguments>
<StartWorkingDirectory>
</StartWorkingDirectory>
<EnableENC>False</EnableENC>
<AlwaysStartWebServerOnDebug>True</AlwaysStartWebServerOnDebug>
</WebProjectProperties>
</FlavorProperties>
</VisualStudio>
</ProjectExtensions>
</Project>

support.csproj vspscc file
listed below

""
{
"FILE_VERSION" = "9237"
"ENLISTMENT_CHOICE" = "NEVER"
"PROJECT_FILE_RELATIVE_PATH" = ""
"NUMBER_OF_EXCLUDED_FILES" = "0"
"ORIGINAL_PROJECT_FILE_PATH" = ""
"NUMBER_OF_NESTED_PROJECTS" = "0"
"SOURCE_CONTROL_SETTINGS_PROVIDER" = "PROVIDER"
}

jkirkerx12-Apr-12 11:10

12-Apr-12 11:10

This is my file, for the first file you posted, in which you just showed the tail of it. My file says not to use IIS Server for debugging, Auto Assign the Port, so instead of 8080, use 2566.

I don't how to change the values using Visual Studio, I did that back in 2005, and have never changed them since. You should be able to hand edit your file, to get you going in Visual Studio at least, by pressing F5 to run your program.

XML

<ProjectExtensions>
    <VisualStudio>
      <FlavorProperties GUID="{349c5851-65df-11da-9384-00065b846f21}">
        <WebProjectProperties>
          <UseIIS>False</UseIIS>
          <AutoAssignPort>True</AutoAssignPort>
          <DevelopmentServerPort>2566</DevelopmentServerPort>
          <DevelopmentServerVPath>/</DevelopmentServerVPath>
          <IISUrl>
          </IISUrl>
          <NTLMAuthentication>False</NTLMAuthentication>
          <UseCustomServer>False</UseCustomServer>
          <CustomServerUrl>
          </CustomServerUrl>
          <SaveServerSettingsInUserFile>False</SaveServerSettingsInUserFile>
        </WebProjectProperties>
      </FlavorProperties>
    </VisualStudio>
  </ProjectExtensions>

This is the 2nd file you posted, csproj. StartAction Tag on mine is CurrentPage, you don't need to edit this file, your file says always start at the beginning.

Once again, I don't how to change the values in the file using Visual Studio, but changing the values in the 2 files will allow you to load the project, press F5, and run the web application in your default browser. The default browser is the one you choose, when the Windows Dialog asked, use this as default browser.

XML

<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <PropertyGroup>
    <ProjectView>ShowAllFiles</ProjectView>
  </PropertyGroup>
  <ProjectExtensions>
    <VisualStudio>
      <FlavorProperties GUID="{349c5851-65df-11da-9384-00065b846f21}" xmlns="">
        <WebProjectProperties>
          <StartPageUrl>
          </StartPageUrl>
          <StartAction>CurrentPage</StartAction>
          <AspNetDebugging>True</AspNetDebugging>
          <SilverlightDebugging>False</SilverlightDebugging>
          <NativeDebugging>False</NativeDebugging>
          <SQLDebugging>False</SQLDebugging>
          <PublishCopyOption>RunFiles</PublishCopyOption>
          <PublishTargetLocation>
          </PublishTargetLocation>
          <PublishDeleteAllFiles>False</PublishDeleteAllFiles>
          <PublishCopyAppData>True</PublishCopyAppData>
          <ExternalProgram>
          </ExternalProgram>
          <StartExternalURL>
          </StartExternalURL>
          <StartCmdLineArguments>
          </StartCmdLineArguments>
          <StartWorkingDirectory>
          </StartWorkingDirectory>
          <EnableENC>False</EnableENC>
          <AlwaysStartWebServerOnDebug>True</AlwaysStartWebServerOnDebug>
          <EnableWcfTestClientForSVC>False</EnableWcfTestClientForSVC>
        </WebProjectProperties>
      </FlavorProperties>
    </VisualStudio>
  </ProjectExtensions>
</Project>

Setting up IIS7 on Vista and Win7 for ASP.Net is sort of tricky. Even I have trouble with it. I wrote a program that does it for me automatically. I will post something you can paste in cmd window and run.

dcof12-Apr-12 12:22

12-Apr-12 12:22

Thank you for your Help! I have the following additional items to mention:

1. You say,"My file says not to use IIS Server for debugging, Auto Assign the Port, so instead of 8080, use 2566.". If I want to debug, then what web server will I be using for debugging the code? Would I be using cassini the built in development web server?
Can you tell me when I would be using cassini versus iis on my workstation? i want to develop the code usingh iis.

2. Why do I want to uninstall the IIS that my netwwork administator setup for me? Do you think he installed something wrong? he told me that I need to use IIS 7 (but it has to be compatible with IIS 6). 
 Here are some of the notes the network administator wrote for how to install IIS on the production web server? Do  you think it will make a difference on what you suggest I try?

Here are the network administrators notes:
The network administrator told me that he did the following for me also Since the following occurs for production: Perform a default installation of the IIS Role Services with the additional inclusion of the entire "IIS 6 Management Compatibility" pack. The entire list of check boxes should include items like Static Content, Default Document, Directory Browsing, IIS Management Console, IIS 6 Management Compatibility, IIS 6 Metabase Compatibility, IIS 6 WMI Compatibility, IIS 6 Scripting Tools, and the IIS 6 Management Console.
  
 Would I need to do something like the following since this occurs for the production website:
 • Once the installation has completed, in the Start Menu right-click the "Command Prompt" shortcut and select "Run as Administrator". In the command prompt window browse to the "C:\Windows\Microsoft.NET\Framework64\v2.x.xxx" directory.
 • Run the following command:
 aspnet_regiis.exe -i
  
 Would I need to change the option for aspnet_regiis.exe?
  
 Also for your information in production the network administrator does the following however I do noth think it applies to me. If it does, can you tell me what I should change for my own installation:
 7) Expand the "" object in the tree found in the left pane. Under "Sites" remove the "Default Web Site", and then under "Application Pools" remove the "DefaultAppPool" and "Classic .NET AppPool" application pools.
 8) Create a new application pool. Name this pool Support and set it to use the ".NET Framework v2.x.xxxx" and the "Integrated" managed pipeline mode. Make sure "Start application pool immediately" is checked and click the "Ok" button.

jkirkerx12-Apr-12 12:53

12-Apr-12 12:53

dcof wrote:
1. You say,"My file says not to use IIS Server for debugging, Auto Assign the Port, so instead of 8080, use 2566.". If I want to debug, then what web server will I be using for debugging the code? Would I be using cassini the built in development web server?
Can you tell me when I would be using cassini versus iis on my workstation? i want to develop the code usingh iis.

Your file says to use IIS Web Server. I said do not use IIS Web Server. The port 8080 is a old port number used for inhouse web projects, 2566 will do for now.

I'm just trying to get your project back to basics, and to get rid of all of the customizations made to your project, so you can evolve on your own. You need to setup your computer to be a development machine, to work on your project first.

dcof wrote:
2. Why do I want to uninstall the IIS that my netwwork administator setup for me? Do you think he installed something wrong? he told me that I need to use IIS 7 (but it has to be compatible with IIS 6).

No No No.

You never indicated that you were setting up your production web server. I assumed that you were still trying to make a development computer to work on the project. Don't run my scripts on your production web server, if fact, get your development computer working first, then when your skill level increases, setup your production web server. Your not ready to deploy on a production IIS7 web server, save that for last - Why, They are 2 different systems. 1 system at a time, so start at development on your computer, make sure it works first, then do the production, and make sure it works correctly.

dcof wrote:
Also for your information in production the network administrator does the following however I do noth think it applies to me. If it does, can you tell me what I should change for my own installation:

In a production enviroment, you will want to create an independent AppPool, so that is correct. Don't forget to assign the support app pool to the website.

FYI

You can install the web application on the server, and use VS to work on it, but I don't recommend it. Always work directly on a development machine and test test test, then final test on a production server with a test website, so you don't crash the main website.

I have to go bowling now, be back tomorrow.

dcof12-Apr-12 18:15

12-Apr-12 18:15

Thank you very much for your assistance!

You are right that I want to setup my own workstation first so that I can test code that I will be developing.
Once the code is working, I will then figure out how to deploy the code to production.

Do you think I need to be concerned with working with IIS 7 (that is compatible with IIS 6)? From what I understand from the network administrator, the original web application was written with II6 and as not been converted to IIS7. Basically it is really working like under IIS 6.

In all, I thought my development environment on my workstation should be as close to production as possiible. That way there should be very little differences between my workstation and production.
However as you can see, I learned the better way from you.

Also for your information, I am the only programmer at my small company. My small computer is currently using a new contract shop to work on items that I think I can not handle yet.

jkirkerx13-Apr-12 7:38

13-Apr-12 7:38

IIS6 compatibility is not what you think it is.

Back in VS 2005, you were able to develop a web application, and make an installation program for it, in which the install program was able to access the metabase of IIS6 objects, and completely setup your IIS6 for you, with no programming knowledge.

IIS7 is a complete rewrite, and no longer uses a metabase to store values, So if you need to talk to a metabase object, you need the II6 compatibility.

You technically don't need it, but there is a small caveat to one thing that it does, that's why I included it.

dcof13-Apr-12 9:08

13-Apr-12 9:08

Thank you for explaining why i need IIS 6!

Yesterday you had indicated that I should remove the IIS that my network administrator installed for me.

When I look at control panel-->uninstall programs, I do not see IIS as something I can uninstall.

I do know that I have IIS as a service since when I look at the
control panel-->system & security-->administrative tools-->then I find that IIS 6.0 Manager and IIS manager is installed on my workstation.

However since IIS is not listed as a program that I can uninstall, I do not know how to uninstall the IIS that the network administrator setup for me.

Thus since you believe I need to install another version of IIS that connects to .net correctly, can you tell me how to uninstall the IIS the network administrator setup for me?

By the way, I do have admin rights on my workstation.

jkirkerx13-Apr-12 9:42

13-Apr-12 9:42

It's the button to the left, 3rd down, Windows Components

dcof12-Apr-12 20:01

12-Apr-12 20:01

XML

Between your two scripts that you supplied, you are saying the following:
1. To get started, I will not be using IIS to test the web application. I will be using the default web server in visual studio 2010 called cassini. Here is where I obtained the opinion from:
From the "http://msdn.microsoft.com/en-us/library/aa983445.aspx" url, I found that you recommend the settings whould be set to the following:
a. <UseIIS>False</UseIIS>Use Local IIS Web server -Specifies that Visual Studio will test your application on the local IIS or IIS Express Web server instead of the Visual Studio Development Server. 
b. <AutoAssignPort>True</AutoAssignPort>Specifies that Visual Studio should select a random HTTP port on the development computer to send requests to. This HTTP port is used to test the Web application project by using the built-in Visual Studio Development Server.
c. <DevelopmentServerVPath>/</DevelopmentServerVPath>- I am using the default development server path.
2. I will go to the control panel-->add/remove programs and then delete IIS that was installed by the network administator.
3. I will then go to the general windows program and type in the command scipt you gave me. This will properly install iis 7/6 to work with my visual studio.
From the above, after I run the PkgMgr.exe, my visual studio.net will be tied into iis.
From what I can gather, I will be still running my visual studio 2010 with the default web server cassini. However when I want to actually connect my visual studio.net 2010 to working with IIs, I will need to change my settings to the following:
<UseIIS>True</UseIIS>
 <AutoAssignPort>False</AutoAssignPort>
 <DevelopmentServerPort>2256</DevelopmentServerPort>
 <DevelopmentServerVPath>/SUPPORT</DevelopmentServerVPath>
 <IISUrl>http://localhost:8080/support</IISUrl>

When I can ready to deploy the application to production, I will need to do the comments you made below:
As far as programming IIS7 server, set the root path to the folder you put the project in in Default Web Site. Then on the far right, set the bindings to port 80, click on Default Documents, and enter the default document name, usually Default.aspx

modified 13-Apr-12 2:10am.

jkirkerx13-Apr-12 7:48

13-Apr-12 7:48

I've never used Cassini, but I took the time just now to learn what it is. Visual Studio comes with WebDev, a small compact program that will execute your asp.net project, and allow you to step or walk through code called debugging.

You have to be able to walk through code in order to fix your mistakes.

Cassini is small web server that a developer can include in there distribution royalty free, and allows for easy setup on a work station. Cassini is unsafe for production use, and is easy to hack.

The purpose of setting up IIS7 on your development computer, is so you can test your html markup in other browsers, to make sure your website project looks and feels the same across all platforms.

dcof13-Apr-12 8:51

13-Apr-12 8:51

Thanks for all your help!

The *csproj that you gave me yesterday, makes me think I am using cassini. I do not see how I am using IIS. The option to use IIS is set to false\ in the *csproj file.

Thus can you tell me how and/or show me a url that explains how my visual studio.net is connected to and using iis?

Is the connection for Visual studio to use IIS in the script that you gave me to rebuild IIS? If so, can you tell me how this connection is setup?

jkirkerx13-Apr-12 10:02

PkgMgr script to install IIS7

13-Apr-12 10:02

There is no relationship between IIS Server and Visual Studio, they are 2 different programs.

Visual Studio is how you create web applications, and test them to make sure they work. You test them in the WebDev, F5 Run in Visual Studio

IIS Server is just a web server program on your computer if your running Windows XP Professional, Vista Business +, then you can use that to host the web application that you made. You use the IIS Web Server on your computer to test your web app with Internet Explorer 8 and 9, Sarfari and Firefox, to make sure they look the same in each browser.

You cannot debug or step through code with IIS Web Server. The WebDev is Visual Studio is for Stepping through code.

Forget about the Cassini, it's confusing you. But if you were running Windows XP Home Edition, or Vista Basic, then you would need Cassini to host your web application, because you need a web server for asp.net for final testing.

I have no clue why your previous developer setup his development computer in such a manner, unless he/she is trying to make the project much more complex than it needs to be, or does not want you to succeed.

1. Write and test your program in Visual Studio, or notepad if your really good.

2. Run the entire program in IIS Server on your computer on several browsers, and run a visual test with your eyes, check for spacing errors, or things not lining up right. Check and make sure your color pallet is pleasing, if your fonts are too large or small. It's a good quick way to run many test without having to leave your desk.

jkirkerx12-Apr-12 11:32

12-Apr-12 11:32

This is the script to properly install IIS7 Server for asp.net
Copy and paste it into your cmd window, may take 20 minutes to run, oh, uninstall IIS 7 server first, add/remove programs, windows components, uncheck IIS Server, and all it's child selections.

cmd.exe /c Start /w PkgMgr.exe /iu:IIS-WebServerManagementTools;IIS-IIS6ManagementCompatibility;IIS-IIS6ManagementCompatibility;IIS-Metabase;IIS-WMICompatibility;IIS-LegacyScripts;IIS-LegacySnapIn;IIS-ManagementConsole;IIS-ManagementScriptingTools;IIS-ManagementService;IIS-WebServerRole;IIS-WebServer;IIS-ApplicationDevelopment;IIS-ASPNET;IIS-NetFxExtensibility;IIS-ASP;IIS-CGI;IIS-ISAPIExtensions;IIS-ISAPIFilter;IIS-ServerSideIncludes;IIS-CommonHttpFeatures;IIS-DefaultDocument;

If you need to intialize the Global Assembly Cache because you got the Server Error 500 GAC page in white with large red letters

aspnet_regiis.exe -ga aspnet

If you need to intialize scripts

aspnet_regiis.exe -i

As far as programming IIS7 server, set the root path to the folder you put the project in in Default Web Site. Then on the far right, set the bindings to port 80, click on Default Documents, and enter the default document name, usually Default.aspx

That's the best I can do from a post, hope that helps you move forward

dcof12-Apr-12 6:58

12-Apr-12 6:58

I have NOT solved the problem. I just clicked OK since I wanted to ask the question a different. If you look at my other open thread in asp.net, you will me original questions stated another way.

In your response to your good suggestion you had earlier, I did ask the network administrator to open port 8080. The network administrator says symantec requires port 8080 to be open for everyone at my company. Is there a way to check if port 8080 is open on my workstation? if so, how do you accomplish that task.

The network administrator has installed IIS on my computer, but has not configured it to work with the visual studio.net 2010 on my workstation.

The network administrator told me that he did the following for me also Since the following occurs for production: Perform a default installation of the IIS Role Services with the additional inclusion of the entire “IIS 6 Management Compatibility” pack. The entire list of check boxes should include items like Static Content, Default Document, Directory Browsing, IIS Management Console, IIS 6 Management Compatibility, IIS 6 Metabase Compatibility, IIS 6 WMI Compatibility, IIS 6 Scripting Tools, and the IIS 6 Management Console.

Would I need to do something like the following since this occurs for the production website:
• Once the installation has completed, in the Start Menu right-click the “Command Prompt” shortcut and select “Run as Administrator”. In the command prompt window browse to the “C:\Windows\Microsoft.NET\Framework64\v2.x.xxx” directory.
• Run the following command:
aspnet_regiis.exe -i

Would I need to change the option for aspnet_regiis.exe?

Also for your information in production the network administrator does the following however I do noth think it applies to me. If it does, can you tell me what I should change for my own installation:
7) Expand the “<webservername>” object in the tree found in the left pane. Under “Sites” remove the “Default Web Site”, and then under “Application Pools” remove the “DefaultAppPool” and “Classic .NET AppPool” application pools.
8) Create a new application pool. Name this pool Support and set it to use the “.NET Framework v2.x.xxxx” and the “Integrated” managed pipeline mode. Make sure “Start application pool immediately” is checked and click the “Ok” button.

SaurabhSavaliya13-Apr-12 0:01

SaurabhSavaliya

13-Apr-12 0:01

Hi,

You are absolutely right dudee.....

Saurabh

dcof13-Apr-12 4:31