Home All Groups Group Topic Archive Search About

DLL PROBLEM ON PRODUCTION - urgent!!!

Author
31 May 2006 6:36 PM
nish
hi,

i upgraded from vs2003 to vs2005.
upgraded from framework 1.1 to 2.0.
did a conversion on my code.

my site is working on my local machine, however it is failing on
production.
i believe the problem is with the dll file.  the dlls are now being
stored in temporary asp.net files folder.  the dll files within the
/bin/ folder have been EXCLUDED from the project.  this works fine on
my local machine.

i copied over my files on to the production server and the sites work
fine except that all the datasets that were CACHED (within global.asax)
are now all null.  I am receiving a nullreference exception.

my question is as follows:

there is no dll to be found on the production machine since nothing was
compiled there and vs2005 was not installed.  in this case should i
copy the dlls within my /temporary asp.net files/ folder into the same
folder in production???
will this fix the error.

please advise.
thanks,
nisha

Author
31 May 2006 11:21 PM
Cowboy (Gregory A. Beamer) - MVP
They should work fine in the /bin. I do not have time to test this,however.

One option I can think of is use the precompile option for websites, which
compiles the entire site into a DLL. Then, deploy the precompiled site. The
help file has info, or you can search MSDN for info. See if that helps.

It prevents dropping a lot of the files on the fly, but it should be another
option that might work.

Dropping in Temp ASP circumvents the system and probably will NOT work.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************


Show quote
"nish" wrote:

> hi,
>
> i upgraded from vs2003 to vs2005.
> upgraded from framework 1.1 to 2.0.
> did a conversion on my code.
>
> my site is working on my local machine, however it is failing on
> production.
> i believe the problem is with the dll file.  the dlls are now being
> stored in temporary asp.net files folder.  the dll files within the
> /bin/ folder have been EXCLUDED from the project.  this works fine on
> my local machine.
>
> i copied over my files on to the production server and the sites work
> fine except that all the datasets that were CACHED (within global.asax)
> are now all null.  I am receiving a nullreference exception.
>
> my question is as follows:
>
> there is no dll to be found on the production machine since nothing was
> compiled there and vs2005 was not installed.  in this case should i
> copy the dlls within my /temporary asp.net files/ folder into the same
> folder in production???
> will this fix the error.
>
> please advise.
> thanks,
> nisha
>
>
Author
1 Jun 2006 7:46 PM
nish
hi gregory,

can you please provide some more details or a link, i was unable to
find any information on this.
i dropped the idea of copying over the dlls into the temp asp folder.

Thanks,
nisha

Cowboy - MVP (Gregory A. Beamer) wrote:
Show quote
> They should work fine in the /bin. I do not have time to test this,however.
>
> One option I can think of is use the precompile option for websites, which
> compiles the entire site into a DLL. Then, deploy the precompiled site. The
> help file has info, or you can search MSDN for info. See if that helps.
>
> It prevents dropping a lot of the files on the fly, but it should be another
> option that might work.
>
> Dropping in Temp ASP circumvents the system and probably will NOT work.
>
> --
> Gregory A. Beamer
> MVP; MCP: +I, SE, SD, DBA
>
> ***************************
> Think Outside the Box!
> ***************************
>
>
> "nish" wrote:
>
> > hi,
> >
> > i upgraded from vs2003 to vs2005.
> > upgraded from framework 1.1 to 2.0.
> > did a conversion on my code.
> >
> > my site is working on my local machine, however it is failing on
> > production.
> > i believe the problem is with the dll file.  the dlls are now being
> > stored in temporary asp.net files folder.  the dll files within the
> > /bin/ folder have been EXCLUDED from the project.  this works fine on
> > my local machine.
> >
> > i copied over my files on to the production server and the sites work
> > fine except that all the datasets that were CACHED (within global.asax)
> > are now all null.  I am receiving a nullreference exception.
> >
> > my question is as follows:
> >
> > there is no dll to be found on the production machine since nothing was
> > compiled there and vs2005 was not installed.  in this case should i
> > copy the dlls within my /temporary asp.net files/ folder into the same
> > folder in production???
> > will this fix the error.
> >
> > please advise.
> > thanks,
> > nisha
> >
> >
Author
2 Jun 2006 2:45 PM
nish
hi gregory,

ok i tried what you suggested, but now i'm receiving the following
error:


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

Parser Error
Description: An error occurred during the parsing of a resource
required to service this request. Please review the following specific
parse error details and modify your source file appropriately.

Parser Error Message: Ambiguous match found.

Source Error:

Line 1:  <%@ page language="c#" inherits="Discovery.desktop,
App_Web_r3o_elen" %>
Line 2:  <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
>
Line 3:  <HTML>


Source File: /HWSETOOLS/desktop.aspx    Line: 1

i have researched but no one seems to have this particular problem.
any ideas?

thanks,
nisha




nish wrote:
Show quote
> hi gregory,
>
> can you please provide some more details or a link, i was unable to
> find any information on this.
> i dropped the idea of copying over the dlls into the temp asp folder.
>
> Thanks,
> nisha
>
> Cowboy - MVP (Gregory A. Beamer) wrote:
> > They should work fine in the /bin. I do not have time to test this,however.
> >
> > One option I can think of is use the precompile option for websites, which
> > compiles the entire site into a DLL. Then, deploy the precompiled site. The
> > help file has info, or you can search MSDN for info. See if that helps.
> >
> > It prevents dropping a lot of the files on the fly, but it should be another
> > option that might work.
> >
> > Dropping in Temp ASP circumvents the system and probably will NOT work.
> >
> > --
> > Gregory A. Beamer
> > MVP; MCP: +I, SE, SD, DBA
> >
> > ***************************
> > Think Outside the Box!
> > ***************************
> >
> >
> > "nish" wrote:
> >
> > > hi,
> > >
> > > i upgraded from vs2003 to vs2005.
> > > upgraded from framework 1.1 to 2.0.
> > > did a conversion on my code.
> > >
> > > my site is working on my local machine, however it is failing on
> > > production.
> > > i believe the problem is with the dll file.  the dlls are now being
> > > stored in temporary asp.net files folder.  the dll files within the
> > > /bin/ folder have been EXCLUDED from the project.  this works fine on
> > > my local machine.
> > >
> > > i copied over my files on to the production server and the sites work
> > > fine except that all the datasets that were CACHED (within global.asax)
> > > are now all null.  I am receiving a nullreference exception.
> > >
> > > my question is as follows:
> > >
> > > there is no dll to be found on the production machine since nothing was
> > > compiled there and vs2005 was not installed.  in this case should i
> > > copy the dlls within my /temporary asp.net files/ folder into the same
> > > folder in production???
> > > will this fix the error.
> > >
> > > please advise.
> > > thanks,
> > > nisha
> > >
> > >

AddThis Social Bookmark Button