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.

On Aug 9, 4:51 pm, Kulgan  wrote:


> 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)

On 9 Aug, 16:04, Alexey Smirnov  wrote:

> On Aug 9, 4:51 pm, Kulgan  wrote:
>
> > 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.

On Aug 9, 6:09 pm, Kulgan  wrote:


> 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.