c:\program files\telerik\openaccess orm\sdk\VEnhance.exe -assembly:C:\Documents and Settings\cgouldj\Desktop\FPI.SetupUtility\SetupUtility\obj\Release\SetupUtility.exe -config:C:\Documents and Settings\cgouldj\Desktop\FPI.SetupUtility\SetupUtility\App.config -debug+ -verbose+ -reference:C:\Documents and Settings\cgouldj\Desktop\FPI.SetupUtility\DataAccessLayer\bin\Release\FPI.DataAccessLayer.dllC:\Documents and Settings\cgouldj\Desktop\FPI.SetupUtility\SetupControls\bin\Release\FPI.SetupControls.dll.
This will teach me to be on the bleeding edge
6 Answers, 1 is accepted
We are happy you solved the problem, but we are really interested in having more information on the problem. Please if you have any insight in the situation or more information, do share it with us.
Regards,
Dimitar Kapitanov
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.
Ths issue was occuring in a project where I had a class library with the Persistent objects and data access layer defined in it, and a second project that is using that library to access the database. The second project is a Winforms application where I am using RadControls for Winforms and it was the source of the issue. When I compiled the class library project there would be no problem, but during the compilation of the Winforms project referencing the class library, the I would receive an OutOfMemory exception and in several cases Visual Studio crashed. I actually have 2 computers that experienced the same thing, the problem stopped after I rebooted the affected PCs.
The actual problem appeard to be the VEnhance call, when the project enhancement is taking place, the crash occurs. I would strongly recommend rebooting the PC after an upgrade occurs.
Thanks for sharing that with us.
Greetings,
Dimitar Kapitanov
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.
I am experiencing the same issue. I use the reverse mapping and start seeing memoy usage going higher and higher.
Do you get an OutOfMemoryException while building your Persistent classes project or while executing the Reversemapping wizard?
Can you attach a debugger (ClrDBG.exe) to the Visual Studio instance, enable 'Break when an Exception is thrown' and then execute the step that generates the error? You can send us the call stack if you get the error.
Here are the steps do attach the debugger
- Open the CLR debugger - dbgCLR.exe, and specify the existing Visual Studio process in 'Attach to Process' via the Tools menu
- Go to the 'Debug->Exceptions' menu item and check the 'CLR exceptions thrown' checkbox
- In the debugging options (available via Tools->Options->Debugging) uncheck the 'Enable Just My Code' option.
- You can now start debugging and execute the steps that reproduce the error and send us the call stack if you get an exception.
Do get back to us in case you need further assistance.
Greetings,
Ady
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.