all groups > asp.net building controls > march 2004 >
You're in the

asp.net building controls

group:

Works in production, not on development server


Works in production, not on development server Schoo
3/25/2004 4:19:26 PM
asp.net building controls:
I have an ASP (with VB as my backend code) I wrote using .NET 2003
(7.1.3088), that works fine on my development workstation, but I copied all
the files from the application directory on my workstation
(c:/inetpub/wwwroot/<projectfile>/*.*), to a folder on the IIS server (W2K
Server) and created a virtual directory to the app and that app gets stuck 3
screens in.

The problem form returns the error "The network path was not found" and
stops on the line of code where I am referencing a DLL control I created in
VS.NET that is designed to return text to the main page:

<cc1:WebText id="Webtext2" runat="server"></cc:Webtext>

Because this works fine on my development workstation but not on the server,
I suspect the problem may be in the way I am 'releasing' it to the dev
server or possibly the way I am referencing controls used in the app. Also,
I am getting another error complaining it can't convert a null into a string
(which makes no sense to me but may be due to the fact I am using session
variables adn it can't find it). Is there a document that outlines a proper
procedure to add references and release ASP.NET apps? Any ideas on where I
need to research from here would be welcome.

Scott

RE: Works in production, not on development server v-felwa NO[at]SPAM online.microsoft.com
3/26/2004 6:00:11 AM
Hi Scott,

Thanks for posting. How do you register the control with the <%@ Register
%> tag? Is there any incorrect path information in the tag?

Please have a check. Here are 2 kb articles that may be useful to you:

HOW TO: Deploy an ASP.NET Web Application Using Xcopy Deployment
http://support.microsoft.com/?id=326355

HOW TO: Deploy an ASP.NET Web Application Using the Copy Project Feature in
Visual Studio .NET
http://support.microsoft.com/?id=326356

I hope this helps.

Regards,

Felix Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
RE: Works in production, not on development server v-felwa NO[at]SPAM online.microsoft.com
3/26/2004 6:14:14 AM
Hi Scott,

In addition, the error message "The network path was not found" is usually
thrown out by some IO related activities. In your user control, do you
attempt to read or write some local path or network share folders?

Regards,

Felix Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Re: Works in production, not on development server Torp
3/26/2004 6:25:54 AM
Felix,

Thanks for the articles. I will read them as they look pertinent. Any
others you can thow at me to read would be appreciated.

I am not really giving the item a path in the <%@ Register %> tag. I add
the dll as a reference to the project and then add it as a component in my
toolbox. Then I drag the component onto my form and go to the HTML tab to
see the tag. I am assuming that when I set it up as a reference, it knows
what I want. I did notice that the dll appears in the project bin folder.
Again: it works in development, but not when I release it to the production
server.

I will look at the articles. Let me know what you think.

Scott

[quoted text, click to view]

Re: Works in production, not on development server v-felwa NO[at]SPAM online.microsoft.com
3/26/2004 7:56:56 AM
Hi Scott,

Thanks for your quick response. I have posted another post and I am not
sure whether you have seen it.

Generally the error "The network path was not found" is thrown by some IO
related activities. Do you access a remote share folder with your user
control?

It is also likely that the error is thrown by ADSI related activities. Do
you use ADSI in your application?

Regards,

Felix Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Re: Works in production, not on development server Schoo
3/29/2004 3:05:11 PM
It took me a while, but I successfully used the copy project tool to release
the project. That will help alot in the future... thanks!

Then I figured out that I am indeed using IO. I learned that the code I
wrote to do that references a local directory for the file on my development
workstation. Of course, this directory is not in the same place on the
server. I modified the code to use request.servervariables parameters to
properly reference the correct location. That seemed to take care of that
issue! YEAAAAAA! WHOOOPIIEEEE!!!! :)

There was a second issue that ended up resulting from my code using data
from a clone table that did not perfectly match the one it was supposed to
be using. I changed the reference to point to the correct tables and the
error message went away.

Thank you for your help!

Scott

[quoted text, click to view]


Re: Works in production, not on development server v-felwa NO[at]SPAM online.microsoft.com
3/30/2004 1:11:25 AM
Hi Scott,

Thanks for your feedback. I am glad to hear that everything works fine now.

Should you have any concerns or new findings regarding this issue, please
feel free to post here.

Have a nice day!

Regards,

Felix Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
AddThis Social Bookmark Button