Visual Studio 2005 ASP NET 2.0 Publish Website issues.

[johnlim20088]

Hi

Hi someone can help me please.

I have a ASP NET 2.0 website with more than 10 web page (aspx).

When I do debug, anything working fine.
Then I publish, it is fine too, and I upload to server.

It is many error about precompiled items in my aspx.

Then I re-publish again WITHOUT CHECK the checkbox ->allow this precompiled site to be updatable.

Anything working fine now.

CHECK or UNCHECK this option, what is the concern?

[Frinavale]

Hi

Hi someone can help me please.

I have a ASP NET 2.0 website with more than 10 web page (aspx).

When I do debug, anything working fine.
Then I publish, it is fine too, and I upload to server.

It is many error about precompiled items in my aspx.

Then I re-publish again WITHOUT CHECK the checkbox ->allow this precompiled site to be updatable.

Anything working fine now.

CHECK or UNCHECK this option, what is the concern?

Seems like a strange problem to me. Everything should work fine without allowing the site to be updateable.

When you publish the site and allow the it to be updatable your source code is copied to the publish destination. If you uncheck this option, Visual Studio does a compile and objects that do not contain your code are copied to the destination.

Checking or un-checking this option should not make a difference to how your website works.

-Frinny

[Plater]

Well what bothers me is the "then i upload it to my server".
That's not how this game works.
Your website must be installed/published to the place where it's going to be running. The IIS server has to know about it and it has to know how to run the backend. The "Publish" should be doing the uploading to your server.

[Frinavale]

Well what bothers me is the "then i upload it to my server".
The "Publish" should be doing the uploading to your server.

I've never been able to get this to work properly..I've always had to publish the website and the move it to my server manually. I've never had any problems, but then again I've always set up the web server exactly the same as my development server.

How do you get this to work??

[Plater]

I've never been able to get this to work properly..I've always had to publish the website and the move it to my server manually. I've never had any problems, but then again I've always set up the web server exactly the same as my development server.

How do you get this to work??

The publish option lets you pick where to publish to. I chose my IIS server (the other computer that actually hosts the website) You have to be sure to setup the FrontPage Extenions (SharePoint) in order for the deploy to work.

(as a side note, they tell you installing the frontpage extensions changes file permisions and might screw up ftp, just a warning)

[Frinavale]

You have to be sure to setup the FrontPage Extenions (SharePoint) in order for the deploy to work.

That's probably my problem.
I'll try this out! Thanks!

[maghi85]

hi,

i too just downloaded microsoft visual studio 2005
i've just put one page on my ASP website

its got a bit of text and a few textboxes with a button
all ASP.NET controls
when i build it the website runs fine
but when i publish it to my website i keep getting this error

it looks like below


Server Error in '/' Application.
--------------------------------------------------------------------------------

Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors > tag within a "web.config " configuration file located in the root directory of the current web application. This <customErrors > tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuratio n>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>


Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirec t" attribute of the application's <customErrors > configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuratio n>
<system.web>
<customErrors mode="RemoteOnl y" defaultRedirect ="mycustompage. htm"/>
</system.web>
</configuration>

[Frinavale]

hi,

i too just downloaded microsoft visual studio 2005
i've just put one page on my ASP website

its got a bit of text and a few textboxes with a button
all ASP.NET controls
when i build it the website runs fine
but when i publish it to my website i keep getting this error

it looks like below

...

Hi Maghi!
Welcome to TDSN.

Your error message is really vague.
Could you possibly change your web.config file so that
[code=xml]
<customErrors mode="RemoteOnl y" defaultRedirect ="mycustompage. htm"/>
[/code]
is changed to
[code=xml]
<customErrors mode="Off" defaultRedirect ="mycustompage. htm"/>
[/code]

Then re-publish your website and run it.
This will let you see a more descriptive error message...post it here so that we can help you out :)

Thanks,

-Frinny

[nateraaaa]

Maghi85 it sounds like there may be a problem with your web.config file. Try adding the following to your web.config file

<identity impersonate="tr ue" />

I usually add this line above <authenticati on mode="Windows" />

Save your web.config file and try running your application again.

Nathan

[Plater]

That is telling you there is an error in your code, however, instead of telling you all the details it is hiding them for security reasons. For developement purposes, you cna change the settings they tell you to so that you can see what the error details are.

[Frinavale]

Maghi85 it sounds like there may be a problem with your web.config file. Try adding the following to your web.config file

<identity impersonate="tr ue" />

I usually add this line above <authenticati on mode="Windows" />

Save your web.config file and try running your application again.

Nathan

Impersonation changes the web user to be a different user...there are security issues that must be taken into consideration when you use this.

I don't think this is necessary to use impersonation yet seeing as we don't even know what the error really is.

-Frinny

[maghi85]

i'm running on a Vista with an IIS 7.0
updating the web.config file and publishing it on to the ftp website gave me the same error
but then i hosted it on to an IIS server on my machine and its working
how do you transfer the website from IIS server on my machine to an ftp website?

[Frinavale]

i'm running on a Vista with an IIS 7.0
updating the web.config file and publishing it on to the ftp website gave me the same error
but then i hosted it on to an IIS server on my machine and its working
how do you transfer the website from IIS server on my machine to an ftp website?

You can just use an ftp client like CuteFTP or WSFTP etc. Just transfer all of the files to your web server.

[maghi85]

You can just use an ftp client like CuteFTP or WSFTP etc. Just transfer all of the files to your web server.

just did that
and it gives the initial error

[Plater]

If you want to see your errors, in your web.config file change the lines to be
[code=xml]
<customErrors mode="Off"/>
[/code]