Hi,
I've noticed that if I make changes in other projects that the reports project depends upon I need to restart Visual Studio in order for the changes to take affect in preview of the report inside VS.
The simplified solution structure looks like this
Solution
-ReportsProject
-EntityFrameworkProject
-OtherClassLibraryProject
E.g. if I make any changes to a method in OtherClassLibraryProject or create a new method that I then use in my reports I need to restart VS in order to see/get the updated version.
Tomas
1 Answer, 1 is accepted
0
Accepted
Hello Tomas,
Every time you recompile an assembly that is used at design-time, Visual Studio copies that assembly to a temporary location and loads the assembly from that location. If you recompile the assembly several times - several identical copies of the assembly are loaded into memory and never get unloaded, unless you close Visual Studio. You can easily confirm this yourself by starting a second instance of Visual Studio and attaching the debugger to the first one.
It seems that this misbehavior is already filed as a bug in connect (Bug ID: 352042), however it is currently postponed by Microsoft.
The problem is that for some reason these duplicated assemblies get in the way of resolving the correct types at design-time. The only method known to us to unload these duplicated assemblies is to restart Visual Studio. This seems to solve the problem temporarily, until you make other modifications and recompile it again.
Kind regards,
Steve
the Telerik team
Every time you recompile an assembly that is used at design-time, Visual Studio copies that assembly to a temporary location and loads the assembly from that location. If you recompile the assembly several times - several identical copies of the assembly are loaded into memory and never get unloaded, unless you close Visual Studio. You can easily confirm this yourself by starting a second instance of Visual Studio and attaching the debugger to the first one.
It seems that this misbehavior is already filed as a bug in connect (Bug ID: 352042), however it is currently postponed by Microsoft.
The problem is that for some reason these duplicated assemblies get in the way of resolving the correct types at design-time. The only method known to us to unload these duplicated assemblies is to restart Visual Studio. This seems to solve the problem temporarily, until you make other modifications and recompile it again.
Kind regards,
Steve
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items