When I double-click my .lqml files in VS2010 it opens the XML file in stead of the Model Designer - I have encountered this problem several times, and it seems that the only remedy is to reinstall the dotConnect for MySQL entirely...
Also when you reinstall the dotConnect for MySQL you have to reinstall the dbMonitor...
VS2010 Designer for .lqml files doesn't show
Hey
Could it be, that you have several things done?
1) Not the actual version of the dotConnect software
2) Tried to copy some generated code into existing code
3) Tried to change the XML Code by hand
4) converted some code from an VS2008 -> VS2010
I figured out such problems as you told, when I have done one or more things written above.
The last updates have made some incremental steps! - Now I never got any of your written problems anymore.
So, download the latest available SW, install it and let's generate the LQML files from the DB. - And NEVER Change the XML by hand!
Hope this helps a little bit...
Could it be, that you have several things done?
1) Not the actual version of the dotConnect software
2) Tried to copy some generated code into existing code
3) Tried to change the XML Code by hand
4) converted some code from an VS2008 -> VS2010
I figured out such problems as you told, when I have done one or more things written above.
The last updates have made some incremental steps! - Now I never got any of your written problems anymore.
So, download the latest available SW, install it and let's generate the LQML files from the DB. - And NEVER Change the XML by hand!
Hope this helps a little bit...
-
StanislavK
- Devart Team
- Posts: 1710
- Joined: Thu 03 Dec 2009 10:48
Apparently, the default editor for .lqml models was changed to the standard XML editor for some reason. To set it back to Entity Developer, please perform the following:
- use the 'Open With' item of the context menu on the model;
- select the 'Entity Developer' item;
- click the 'Set as Default' button.
Normally, it shouldn't be necessary to re-install dbMonitor after re-installing dotConnect for MySQL. If you are encountering any problems with dbMonitor in such case, could you please describe them?
- use the 'Open With' item of the context menu on the model;
- select the 'Entity Developer' item;
- click the 'Set as Default' button.
Normally, it shouldn't be necessary to re-install dbMonitor after re-installing dotConnect for MySQL. If you are encountering any problems with dbMonitor in such case, could you please describe them?
StanislavK:
OK, sounds like that could be the problem - I will try that when it happens again.
With regards to the dbMonitor, it doesn't always hook up to the process being debugged - note that we are developing in MS .NET MVC 2. Sometimes we need to clean the solution, rebuild and then debug for it to hook up to the process.
Zero-G:
1) What do you mean by "actual version" - it is a fully licenced Devart dotConnect for MySQL Professional, version 5.80.190.0?
2) No, for sure didn't do that.
3) Obviously we didn't do that.
4) No, didn't do that either - MVC 2 was not introduced in VS2008.
Auto-generated code is not to be messed with, we are fully aware of that.
OK, sounds like that could be the problem - I will try that when it happens again.
With regards to the dbMonitor, it doesn't always hook up to the process being debugged - note that we are developing in MS .NET MVC 2. Sometimes we need to clean the solution, rebuild and then debug for it to hook up to the process.
Zero-G:
1) What do you mean by "actual version" - it is a fully licenced Devart dotConnect for MySQL Professional, version 5.80.190.0?
2) No, for sure didn't do that.
3) Obviously we didn't do that.
4) No, didn't do that either - MVC 2 was not introduced in VS2008.
Auto-generated code is not to be messed with, we are fully aware of that.
-
StanislavK
- Devart Team
- Posts: 1710
- Joined: Thu 03 Dec 2009 10:48
There are several possible reasons why the dbMonitor application is not tracing database interoperations:
- the Port property of the DbMonitor object does not correspond to the Tools -> Options -> 'Port number ...' setting of dbMonitor.exe;
- dbMonitor.exe was launched after the application was;
- (for web applications) the DbMonitor object is disposed after leaving the page where it was created.
To eliminate the latter possibility, you can, e.g., persist this object in a HttpApplicationState collection. Please see our documentation for a sample of creating a MySqlMonitor instance in this way:
http://www.devart.com/dotconnect/mysql/ ... nitor.html
Please tell us if the problem with dbMonitor occurs when nothing of the above holds.
- the Port property of the DbMonitor object does not correspond to the Tools -> Options -> 'Port number ...' setting of dbMonitor.exe;
- dbMonitor.exe was launched after the application was;
- (for web applications) the DbMonitor object is disposed after leaving the page where it was created.
To eliminate the latter possibility, you can, e.g., persist this object in a HttpApplicationState collection. Please see our documentation for a sample of creating a MySqlMonitor instance in this way:
http://www.devart.com/dotconnect/mysql/ ... nitor.html
Please tell us if the problem with dbMonitor occurs when nothing of the above holds.
This was the solution indeed.
The same thing happened again, and this was indeed the solution - thanks al billion!StanislavK wrote:Apparently, the default editor for .lqml models was changed to the standard XML editor for some reason. To set it back to Entity Developer, please perform the following:
- use the 'Open With' item of the context menu on the model;
- select the 'Entity Developer' item;
- click the 'Set as Default' button.