Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / General / August 2007

Tip: Looking for answers? Try searching our database.

Different Assemblies At Runtime

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Kulgan - 09 Aug 2007 15:51 GMT
Hi

We have a serious problem here with a 1.1 web app that has been
upgraded to 2.0!

Our web app can optionally use Crystal Reports. This means that it
must be compiled on a machine with the Crystal runtime installed on
it. In ASP.NET 1.1 we could then deploy to a production server that
did not have the Crystal Reports runtime assemblies on it providing
that our code that used those assemblies was not executed.

In ASP.NET 2 this seems to have changed. If we build using the Crystal
assemblies but do not deploy them on a server (even if the code that
uses the assenblies is not executed) we get problems with the app. The
most obvious problem is that Forms authentication ticket starts to
"forget" roles that have been attached to it.

Has anyone had any similar problems?

Thanks,

Nick.
Alexey Smirnov - 09 Aug 2007 16:04 GMT
> most obvious problem is that Forms authentication ticket starts to
> "forget" roles that have been attached to it.

I think the problem is not related to CR. Check if your new app is
properly configured on the server (.net version, web.config, etc)
Kulgan - 09 Aug 2007 17:09 GMT
> > most obvious problem is that Forms authentication ticket starts to
> > "forget" roles that have been attached to it.
>
> I think the problem is not related to CR. Check if your new app is
> properly configured on the server (.net version, web.config, etc)

Hi

I agree with you. I think to root problem is probably something to do
with class loading mechanisms in .NET 2. The key is that the
assemblies available at runtime are not the same as the assemblies
available at compile time. Has any had any problems like this before?

Nick.
Alexey Smirnov - 09 Aug 2007 18:20 GMT
> assemblies available at runtime are not the same as the assemblies
> available at compile time.
[...]
> If we build using the Crystal
> assemblies but do not deploy them on a server (even if the code that

You should build application and copy the assembly to your website's
\bin directory.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.