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
|
Hi Guys, Using various versions of light speed up to the nightly build 24th Oct on VS2010 and VS2012 along with Latest version of .Net Demon. With .Net Demon set to only build on saving, whenever I save my lsmodel, .net Demon keeps trying to build constantly - almost as if the lsmodel is constantly changing code - or they are fighting over the files? Closing the lsmodel file, everything goes back to normal and is fine. This happens on my colleagues PC too. Has anybody come across this, know what is causing it or know how to resolve it? Cheers, Sean |
|
|
|
|
When you save the model we will re-generate the code for your domain entities so there is a change taking place. Does .NET Demon have any options for ignoring certain files?
|
|
|
|
|
Hi Jeremy, Thanks for the reply - there are no options in .Net Demon to exclude files, however, since Lightspeed is only generating a .cs file, that should be compiled with no issues. I have switched off all of the options in .Net Demon so it does no auto build etc - but the Lightspeed modeller still stops working correctly upon saving. If I disable .net Demon - Lightspeed is happy. So there is some sort of clash - but I can't work it out? Are you able to install .net Demo trial to see if you are able to replicate this? Cheers, Sean |
|
|
|
|
Hi Sean, Ive installed this and can see the same behaviour. What is occurring is our custom tool (which is registered with Visual Studio to be triggered when the .lsmodel file is modified) is being repeatedly triggered, presumably by .NET Demon since disabling this removes the problem. The endless generation then causes a lock-up. There shouldnt be any reason to continually call the custom tool so this looks like an issue with .NET Demon. No idea why it would be doing this but presumably they think something is changing and are triggering it either directly or indirectly which leads to the behaviour here. So for now you will just need to disable .NET Demon. You might want to ping them to see if its either a known issue or something they could fix.
|
|
|
|
|
Thanks for looking at this Jeremy, Redgate have got back to me - it's a known issue "reference- NEP-684 Incompatibility with Lightspeed from Mindscape." I'm only the second person this year to report this issue though, so it's not a high priority :( Thanks again for checking it out. Cheers, Sean |
|
|
|
