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
|
Is it possible to set the namespace of the generated UnitOfWork independently from the entity classes? |
|
|
|
|
Not directly. You can do it by editing the code generation templates though. |
|
|
|
|
Thanks Ivan.
I do have another query. When I follow the instructions to edit the code generation templates from the blog post you provided, I find that I don't have a "LightSpeed Template File" entry on the property grid of the project that has the LightSpeed model (running VS2010). Is there some trick to enable this? |
|
|
|
|
You may find you need to open a model before VS will display the project setting. |
|
|
|
|
I can confirm that I have open the model and it is still not showing up. Do you have any other suggestions?
I assume that this location will either be stored directly in the project file or the model file - could I add the location manually in xml?
|
|
|
|
|
We did at one point have a bug where this didn't work if the model was in a subfolder of the project. If that's your case, and you're on a build of LightSpeed prior to 3.11, please upgrade to 3.11 or the latest nightly build. Failing that, try closing all documents, closing the solution, restarting Visual Studio, opening the solution and opening your model file. Then check the .csproj file and see if the setting now appears. If that still doesn't work then let me know and I'll show you how to edit it into the .csproj file directly. |
|
|
|
|
It is indeed the case that my model file is in a subfolder of the project. I have the version installed from the nightly build of the 17/Feb (LightSpeed31Professional-20110217.msi). I didn't have any luck when I restarted Visual Studio.
That said, I did have success by creating a new project, and adding a model file. I then looked at the changes in the project file, applied them to my own project, and then everything started working as expected.
Let me know if I can help diagnose the problem any further. |
|
|
|
