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, I just bought the designer and have 2 issues:
Warnung 1 Cannot find a schema that defines target namespace 'http://namespaces.mindscape.co.nz/nhmodel', schema validation skipped. And after clicking on this error message, I am not able to open the designer view again, just the XML view. How do I fix this please? Thanks, Kay |
|
|
Hi Kay, Sorry to hear you're having problems. Would you be willing to share your model so we can try to reproduce the crash? If it contains sensitive information then you can email it to support@mindscape.co.nz, otherwise you can attach it to a forum post using the "Upload a file" button. Thanks! The warning is benign and can be ignored. We will investigate why you are seeing it. The 'always opens as XML' behaviour is a VS2010 bug and the fix is to open the .csproj file in a text editor, locate the .nhmodel file and delete the |
|
|
Hi Ivan, after reinstallation and new installation the crashes stopped so far. Thanks for the fix with the VS2010 bug. I am new to nhibernate and O/R mapping and I must say that your Designer helps me a lot to get a smooth start and I got my own existing project working with your designer and nhibernate (not used an O/R mapper before). But I have to say that your documentation is a bit hard to get started - it's a bit poor ;-) Some kind of a walkthrough with a small project would be nice for beginners. E.g. create a small modell (from DB or to DB), make a select and an update statement, create the sql statements to create the DB when deploying the application, etc. But I guess I have to study nhibernate documentation instead :-) Regards, Kay |
|
|
Glad to hear those issues are resolved. We appreciate the feedback on the documentation and we'll try to get this improved. We agree that a tutorial or screencast would be a really good idea -- I believe we were planning a 'get started' screencast and I'll chase up what happened to this. Thanks again for your comments and suggestions! |
|