This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I am working with my newly upgraded Lightspeed and it is not creating the .cs file for the .lsmodel in my Visual Studio 2008 projects. I am not able to create new LightSpeedContext<unitOfWorkType>() because that unit of work does not exist. I also noticed that if I right click on the .lsmodel now, and choose "Run custom tool", I get this error:
--------------------------- Microsoft Visual Studio --------------------------- The custom tool 'LightSpeedModelGenerator' failed. Method not found: 'Mindscape.LightSpeed.Generator.Integration.Model Mindscape.LightSpeed.Generator.Integration.Model.FromXml(System.String)'. --------------------------- OK --------------------------- May be related? Have I missed a step somewhere?
I uninstalled Lightspeed 3.0 and reinstalled it from a freshly downloaded copy, still is not working as expected.
I'm going to revert back to 2.x for now, but if this error indicates that I have something missing please let me know.
|
|
|
After uninstalling 3.0 and doing a Repair on 2.2, this error appeared as I started up VS and opened my Lightspeed projects. |
|
|
These kinds of designer errors typically indicate that something went wrong during the upgrade and there are bits of both 2.x and 3.0 hanging around and conflicting. Please go to Control Panel and uninstall *all* LightSpeed entries you see there -- you may see more than one! After doing this, you may want to verify that the install directory is empty and that no Mindscape.* DLLs remain in the GAC. Since you have seen the dreaded Package Load Failure dialog, you should then open a Visual Studio command prompt and run devenv /resetskippkgs Otherwise Visual Studio will remember that a previous attempt to load LightSpeed failed and it will silently refuse to load it again. Finally, reinstall LightSpeed 3.0. Let us know if you still see problems! |
|
|
This seemed to help, I did get 3.0 working now. I found a (unrelated) bug along the way.... If you add a new .lsmodel to your project, then rename it, the renaming does not propagate through to the underlying class; the original name remains for class names. My current workaround is to delete the model and add new one with correct name from the beginning.
|
|
|
Hello Steve, This is by design: otherwise renaming your file would break existing code that relies on the old name. To rename the underlying class(es), e.g. the unit of work class, click on the model background, go to the Properties window and edit the Name setting. This is defaulted to the initial filename when the model is created, but you can change it to anything you like, including of course the new filename! Hope this helps! |
|