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
|
Working with DB2 and Visual Studio 2013:
Thanks, John |
|
|
Hi John, re 1: The intention with custom attributes is for you to fully qualify them, however you can add namespaces to the generated code by adding an entry to the Imported Namespaces located in the LightSpeed model tool pane. This is described under the Designer Tips section of the documentation here: http://www.mindscapehq.com/documentation/lightspeed/Working-with-Models-in-the-Visual-Designer/Designer-Shortcuts-and-Tips re 2: We dont currently support Visual Studio 2013, we will be adding in specific support for this when the RTM bits and SDK's for that become available so it may just be a quirk relating to that but check that you are not using the Properties from the context menu (e.g. right click on Project node and select Properties, rather left click the project node and then select the Properties tool pane). e.g. re: 3: We map boolean to DECIMAL(1,0) as a substitute to the lack of a boolean type prior to 9.7. These mappings are part of the designer code and cannot be changed Im afraid.
|
|
|
re 2: Using Visual Studio 2012 I see |
|
|
Unfortunately Im not sure why thats not showing for you then. What type of project are you working with and is it possible to send us through a copy of that project so we can check how it looks on a machine here?
|
|
|
I created a new project, added a model and move my model to the new project. The Lightspeed Template File property is showing up in the new project. Thanks |
|
|
Spoke too soon! The property disappeared again. So, to test, I created a new solution; added a WPF project; added a model to that. All fine. Added a class library; added a model; all fine. Added an existing project. All fine. Added another. Property missing from both WPF project and class library. Restarted VS. All fine. Back to original project. Restarted VS. Property shows up fine. I noticed that VS 2012 is rather fragile now. Moving from project to project to check on property can cause VS to stop working and restart. Happened 3 times in the course of these tests. |
|
|
Hmm, what else do you have installed in terms of Visual Studio addins or extensions? Sounds like either something is causing the property to be ignored or it could just be a case that your Visual Studio instance isnt too happy. Do you have another machine you can check these projects against to see if its consistent behaviour or just isolated to that one machine? If you are able to send us some of the affected project files we can check that here for you.
|
|