470,612 Members | 2,522 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 470,612 developers. It's quick & easy.

asp.net 1.1 code build/deployment issue

Hi I've a development server, where I've set up and copied the code (ASP.NET 1.1 webapp in .NET 2003) from an existing QA server. But I'm having issues, seeing my code changes. When I make some change (aspx or code behind) and build the code, I'm not able to see the changes unless I deploy the dll in deploy directory, even when i'm executing the code in debug mode. i'm able to see the changes reflected when i open the url as http://localhost/logon.aspx, after I copy the dll from build directory to deploy directory. But why is it not showing in debug mode instantly , when i build the code.

Another associated issue is when I refer the same website as http://servername/logon.aspx on the development server browser, the javascript code doesn't appear to be working, as the button click events don't fire, any code writen in java script doesnt work, like calendar controls etc. But when I open the same url from another machine by the same url http://servername/logon.aspx, everything works fine, including javascript and my deployed changes. What could be the reason of such behaviour?


Your help is greatly appreciated Thanks
Jan 7 '08 #1
5 1775
Plater
7,872 Expert 4TB
Hi I've a development server, where I've set up and copied the code (ASP.NET 1.1 webapp in .NET 2003) from an existing QA server. But I'm having issues, seeing my code changes. When I make some change (aspx or code behind) and build the code, I'm not able to see the changes unless I deploy the dll in deploy directory, even when i'm executing the code in debug mode. i'm able to see the changes reflected when i open the url as http://localhost/logon.aspx, after I copy the dll from build directory to deploy directory. But why is it not showing in debug mode instantly , when i build the code.
If the location for the website is set to be X, then trying to run/debug it will look for the webpage in X, if X does not have your recent changes, it will still be using your old ones.
What is the setup you are using for this webapplication?
(where are the code files stored, where does it deploy to, are you using PUBLISH to send it out, etc)


Another associated issue is when I refer the same website as http://servername/logon.aspx on the development server browser, the javascript code doesn't appear to be working, as the button click events don't fire, any code writen in java script doesnt work, like calendar controls etc. But when I open the same url from another machine by the same url http://servername/logon.aspx, everything works fine, including javascript and my deployed changes. What could be the reason of such behaviour?
Sounds like your dev server's browser is probably doing one or more of the following:
blocking all javascript
blocking a session cookie
blocking dhtml(javascript?) code
Jan 7 '08 #2
If the location for the website is set to be X, then trying to run/debug it will look for the webpage in X, if X does not have your recent changes, it will still be using your old ones.
What is the setup you are using for this webapplication?
(where are the code files stored, where does it deploy to, are you using PUBLISH to send it out, etc)
I'm not using any setup program, for deployment, using xcopy method.
I have a virtual directory (deploy directory) in D:\MIMS folder, and my build directory is E:\Projects\Nike\RibSystem\Clients\Nike\NikeRIBWeb App. I build my code in D drive and deploy the dlls/aspx pages in E drive.
NikeRibWebApp is the name of virtual directory, and in IIS, in the Website properties - Home Directory tab, LocalPath is set to D:\MIMS and in the virtual directory properties, local path is set to E:\Projects\Nike\RibSystem\Clients\Nike\NikeRIBWeb App. Please let me know if i'm missing anything.

Sounds like your dev server's browser is probably doing one or more of the following:
blocking all javascript
blocking a session cookie
blocking dhtml(javascript?) code

Thanks for detailed reply.
If dev server's browser would have been blocking javascript, opening the url http://localhost in the same dev server's browser should have also behaved the same way, but with localost, it works fine.
Jan 8 '08 #3
Plater
7,872 Expert 4TB
Thanks for detailed reply.
If dev server's browser would have been blocking javascript, opening the url http://localhost in the same dev server's browser should have also behaved the same way, but with localost, it works fine.
Could be set to allow javascript on localpages, something about local pages being in a trust zone maybe?
Jan 8 '08 #4
I'm not using any setup program, for deployment, using xcopy method.
I have a virtual directory (deploy directory) in D:\MIMS folder, and my build directory is E:\Projects\Nike\RibSystem\Clients\Nike\NikeRIBWeb App. I build my code in D drive and deploy the dlls/aspx pages in E drive.
NikeRibWebApp is the name of virtual directory, and in IIS, in the Website properties - Home Directory tab, LocalPath is set to D:\MIMS and in the virtual directory properties, local path is set to E:\Projects\Nike\RibSystem\Clients\Nike\NikeRIBWeb App. Please let me know if i'm missing anything.
Jan 8 '08 #5
Could be set to allow javascript on localpages, something about local pages being in a trust zone maybe?

Yes, that solved my problem :-))))
I added servername url in Site list. Localhost was already there
Thanks so much....

But referring to first part of Q, before deployment of code to deploy directory, in debug mode, I should be able to see my code changes when I build and execute the code, which I'm not able to see. Why is it so?
Jan 8 '08 #6

Post your reply

Sign in to post your reply or Sign up for a free account.

Similar topics

2 posts views Thread by Felix | last post: by
reply views Thread by George Harig | last post: by
27 posts views Thread by Jonathan Wood | last post: by
1 post views Thread by =?Utf-8?B?Q2h1Y2sgUA==?= | last post: by
8 posts views Thread by Alexander Llew Wykel | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.