G
Guest
I'm sure this is an easy one for someone out there
I'm trying to access the QuickStart files in my .NET FrameWorkSDK however I'm having problem
When I follow the links in the SDK to reach the directory http://localhost/quickstart/ASPPlus/ it opens the default.aspx just fine however it displays no imbedded content beyond the "ASP.NET" toolbar are a few microsoft links at the top. It appears to download the embedded file (labeled doc/quickstart.aspx) but depending on my IIS directory settings or what I have labeled as my default "Open with" application it chooses to open this quickstart.aspx differantly. Originally my default application for type aspx's was MS Dev Studio so by opening a web document, my dev studio open to display to souce code content
I managed to find a website on the web labeled http://www.csharpfriends.com/quickstart/aspplus/ which an identical copy of this quickstart and this works perfectly (despite only minor differances in source
So I suspect that the problem lies somewhere in my IIS settings. IIS setup seems to be a bit of a black art. Can anyone help me diagnose this problem
I'm trying to access the QuickStart files in my .NET FrameWorkSDK however I'm having problem
When I follow the links in the SDK to reach the directory http://localhost/quickstart/ASPPlus/ it opens the default.aspx just fine however it displays no imbedded content beyond the "ASP.NET" toolbar are a few microsoft links at the top. It appears to download the embedded file (labeled doc/quickstart.aspx) but depending on my IIS directory settings or what I have labeled as my default "Open with" application it chooses to open this quickstart.aspx differantly. Originally my default application for type aspx's was MS Dev Studio so by opening a web document, my dev studio open to display to souce code content
I managed to find a website on the web labeled http://www.csharpfriends.com/quickstart/aspplus/ which an identical copy of this quickstart and this works perfectly (despite only minor differances in source
So I suspect that the problem lies somewhere in my IIS settings. IIS setup seems to be a bit of a black art. Can anyone help me diagnose this problem