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 there, I get a NullReferenceException when I want to displaying SQL-Log for database changes: |
|
|
A couple of questions: * If you have VS2008 installed, do you also get this error on VS2008? * Are you using the English or German version of Visual Studio? Thanks! |
|
|
Hi, * VS2008 isn't installed anymore. * It an englisch VS2010 Professional * W7 64Bit German * LightSpeed31Professional-20101112 Regards, Sörnt |
|
|
Hmm, I can reproduce this problem on non-English versions of Visual Studio (and have pinged Microsoft to see if there is a non-kludgy resolution for it), but with an English version of VS2010 on a non-English OS it all seems to work fine. Can you confirm that you are definitely running an English version of Visual Studio? If so, could you provide me with a screenshot of the File > New > File dialog, General tab, please? Thanks! |
|
|
I am allmost sure :-)
Kind regards, |
|
|
Certainly looks English! I would still like to see a screenshot of the File > New > File dialog (General tab) though if possible -- NOT the New Project or New Class dialog, but the New File dialog you get when selecting File > New > File from the top-level menu. (It should have Text File in it, probably at the top.) Thanks! |
|
|
|
|
|
Well, I'm stumped by this I'm afraid -- can't reproduce it and can't see what might be causing the error. I've put a candidate workaround into the next nightly build. I can't promise it will fix the problem for you, because I don't know exactly what the problem is, but it handles the main suspects! The downside of the workaround is that it will result in a file being created in your temporary directory each time you show a SQL log -- and these files will not be cleaned up automatically. I have some ideas on how I may be able to clean this up but I need to know first of all whether the candidate fix works for you at all -- let me know! |
|
|
Installed the latest version (LightSpeed31Professional-20101117.msi) and the error is still there. After the crash I saw a "~vsB663.sql" file (the timestamp correlates with the crash) - But it is empty. Do want to have a remote access to my PC? |
|
|
I've committed some additional diagnostics which will be in the next nightly build. Could you give it a try when it's available (about 1200 UTC) and let me know the EXACT error message you see please? Thanks! |
|
|
Installed "LightSpeed31Professional-20101118.msi" while "x:\temp\tmpE890.tmp" contains the the SQL for altering the database.
-- This file contains a log of the SQL statements that LightSpeed ran The X: Drive is a RAM-Disc. Regards, |
|
|
This appears to be an issue with an internal API failing within Visual Studio. We've never seen this on any other machine, and we don't know what would cause it. I'm going to investigate for a fix, but can't make any promises. I'll keep you informed. In the meantime, I'm making some further changes in the next nightly build so that in a failure scenario it opens the dump file in Visual Studio. This still leaves files in your temp directory, but will at least make it a bit easier for you to review the logged SQL and save it elsewhere. |
|
|
Thank you, Ivan! Regards, |
|
|
Problem fixed as per here: http://stackoverflow.com/questions/3526906 |
|