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 installed VS2010 beside my VS2008. Before moving everything to VS2010, I would to ask if the nightly builds support VS2010? Kind regards, Sörnt |
|
|
|
|
Not fully, I'm afraid. There is a VS2010 compatible version of the designer, but: * this is a separate download (available from the store) We are hoping to fold 2010 support into the nightly builds sometime this week, but we are not making any promises yet, and initial drops may not be fully integrated into the install process. Keep an eye on the blog or the Twitter feed: we'll make announcements once full support starts rolling out. The LightSpeed runtime DLLs do support VS2010 to the best of our knowledge (and C# or VB code generated using the VS2008 designer should therefore build in VS2010 if required). |
|
|
|
|
We now eagerly await the VS2010 compatible nightly build :) |
|
|
|
|
Great guys, you are awsome! I'm awaiting too.. :) |
|
|
|
|
I'm having trouble using the designer in 2010. It's 2010 Ultimate (RTM) and the latest nightly build and alpha. I installed them in that order (Lightspeed first, Designer second). The environment is Windows 7 Professional x64. I see that the LightSpeedModel.zip is in the template folder, but it doesn't show up in the "New Item->Data" list. I can open a model created in VS 2008 (couldn't do that before the nightly build).
Thanks!
James |
|
|
|
|
Do you see an *uncompressed* folder named LightSpeedModel.zip in the ItemTemplatesCache folder (under the CSharp / Data subfolder)? If not, try opening a Visual Studio command prompt and running devenv /installvstemplates. (The entry under ItemTemplates is a sort of master copy of the template, but it doesn't become active until unpacked into ItemTemplatesCache. /installvstemplates forces VS to re-unpack all the master copies.) |
|
|
|
|
Yes, under the 1033 subfolder. Here is where it is on my system: C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\ItemTemplates\CSharp\Data\1033\LightSpeedModel.zip C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\ItemTemplates\VisualBasic\Data\1033\LightSpeedModel.zip C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\ItemTemplatesCache\CSharp\Data\1033\LightSpeedModel.zip C:\Users\Me\AppData\Roaming\Microsoft\VisualStudio\10.0\ItemTemplatesCache\Visual C#\LightSpeedModel.zip C:\VSInstallDir\ItemTemplates\CSharp\Data\LightSpeedModel.zip C:\VSInstallDir\ItemTemplates\VisualBasic\Data\LightSpeedModel.zip Also have a 'C:\VSRootDir\Xml\Schemas'
|
|
|
|
|
Just to update everyone on how we're progressing with this: it looks like we're not going to be able to integrate the VS2010 designer into the nightly builds this week (there are some complexities with the automated build which are requiring some more substantive changes to the build process than we'd planned, and testing changes to the build process is slow). So the VS2010 designer will be slipping into next week -- hopefully *early* next week! We'll continue to keep you informed as we make progress. |
|
|
|
|
Hello James, Hmm, that layout looks fine (except for the C:\VSInstallDir and C:\VSRootDir which are the result of an interim integration to support systems without VS2008 on them). Can you check for me what are the contents of the ItemTemplatesCache\...\LightSpeedModel.zip directory? If you run devenv /setup or devenv /vsinstalltemplates from a VS2010 command prompt, does that help? |
|
|
|
|
Hi Ivan, I have exactly the same issue. In the folder: C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\ItemTemplatesCache\CSharp\Data\1033\LightSpeedModel.zip the following files exist: CSharp.vstemplate I ran both the devenv commands you mentioned with no success. Regards, Rohan. |
|
|
|
|
Hello James and Rohan, Could you have a look in the VS New Item dialog and see if you have something odd-looking in the Data tab that calls itself "CSharp"? If so could you try clicking on that and see if that creates a LightSpeed model? Thanks! |
|
|
|
|
Okay, I can verify that the item called "CSharp" is in fact the Lightspeed model template. Thanks for looking into it. Regards, Rohan. |
|
|
|
|
It's here! The next nightly build (21 Apr 2010, available from about 1500 GMT) will contain VS2010 support integrated into the main installer. Please ensure that you uninstall the alpha VS2010 designer before installing the nightly. We are aware of a couple of minor outstanding issues with VS2010 support in this release, and are working to resolve these. As always, please report any bugs or problems. |
|
|
|
|
That sounds excellent, I will give it a spin later on. Kind regards, |
|
|
|
|
Hi, just installed it and here is what I found so far: Pros: * installation was smoothly Cons: There are some elements missing at the Toolbox. I missed so far: * the ValueObject (the existing value objects are displayed correctly at my model) Very, very, minor: "* the LightSpeed Icon for the model at the "Add new Item" dialog looks like a MS generic one"
I am running out of time to do more testing right now. Regards, Sörnt |
|
|
|
|
So what's the planned release date for the (production) VS2010 support? Looking forward to it, keep up the good work! |
|
|
|
|
The formal release of VS2010 support will be in LightSpeed 3.1, for which we haven't yet announced a date. In the meantime, we will be fixing the outstanding issues over the course of the next few nightly builds. We do fully support our nightly builds and we do have customers using them in production, so don't let the "nightly" label stop you. |
|
|
|
|
Just to add further to what Ivan is saying here, the VS 2010 support is only really related to the designer integration. The core LightSpeed code hasn't really had anything done to it as part of this process so worst case scenario, your designer may show some bugs for the time being. It doesn't mean the LightSpeed core product isn't in a production ready state though. We'll be putting the finishing touches on our plan for LightSpeed 3.1 to be released shortly and make the announcement soon. The best way to help that move forward is by testing out the current nightly designer in VS2010 and reporting any issues so we can be sure it's ready to be labeled as 3.1 :-) I hope that helps, John-Daniel |
|
|
|
|
Hi, I spend some more time for testing. What I am missing are the follwing items at the toolbox:
Something I expected (but I am not to sure about that) are some .NET 4.0 assemblies at the LightSpeed\Bin folder. I set the target framework to .NET 4.0 for all of my projects. Do I need to deploy also the .NET 3.5 Framework inorder to run my application? If I set the target framework to .NET 4.0 client-Profil (As far as I understand that is a subset with the relevant assemblies for normal desktop application), I get that warning: Warning 417 The referenced assembly "Mindscape.LightSpeed.Linq, Version=3.0.789.12667, Culture=neutral, PublicKeyToken=360c8f37b466ebb2, processorArchitecture=MSIL" could not be resolved because it has a dependency on "System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" which is not in the currently targeted framework ".NETFramework,Version=v4.0,Profile=Client". Please remove references to assemblies not in the targeted framework or consider retargeting your project. and than (of course) some hundreds of errors. I guess you need to refactor your library and create another assembly which contains the web relevant parts. Otherwise I need to deploy the the full .NET framework 4.0 (with the not relevant web part). Kind regards, Sörnt |
|
|
|
|
Thanks for that info. We're aware of the toolbox issue and are working to address it, but it's always useful to have confirmation of what people are seeing. My understanding is that you should not need to deploy the 3.5 Framework to use LightSpeed, because the 4.0 CLR will resolve LightSpeed's System.* dependencies to the 4.0 DLLs rather than the 3.5 DLLs. However we haven't tested in this scenario (our "clean" VS2010 box is a Win7 box, so it has the 3.5 Framework as part of the OS). Regarding the client profile warnings, it is safe to exclude these warnings as long as you are not using the non-client-profile bits of LightSpeed (e.g. HTTP request caching, the Oracle9 provider, etc.). I believe this should suffice because we have customers using LightSpeed with the 3.5 Client Profile in this way. We do not at present plan to break LightSpeed up into client and server builds, but we may consider this as .NET 4 gains more traction and people start to use the Client Profile more extensively. Thanks for the feedback as it helps us to prioritise! |
|
|
|
|
Hello Soernt, You should have all the toolbox items back in the next nightly build (24 April), except for ScalarProcedure which is still causing problems. We've brought back the proper LightSpeed icon in the Add Item dialog too. |
|
|
|
|
Hello Ivan, that nightly build looks excellent! Thank you very much! Sörnt |
|
|
|
|
Can someone check if VS 2010 Designer is creating .cs file when adding new Lightspeed model? I've tried 24 and 26 night build and none of them was creating class file. |
|
|
|
|
Just created a Console application and added a LightSpeedModel. The LightSpeedModel.cs files is created correctly. I have the "LightSpeed30Professional-20100424.msi" from 24. installed. |
|
|
|
|
That's strange. I've found workaround for my problem. I've installed latest night build and I've installed "LightSpeedDesigner.VS2010_20100127.msi" which I've found on my HD. Now when I was creating/updating Lightspeed model .cs file was created/updated. |
|
|
|
|
I'm not certain, but I think the latest nightly build (LightSpeed30Professional-20100430) is missing the SQL 2008 data provider option in the Model Designer. It's in the distributables but something seems to be preventing it's selection in my IDE. |
|
|
|
|
The designer doesn't distinguish between SQL 2005 and 2008: the SqlServer2005 provider works for both. (However, the LightSpeed runtime *does* distinguish between the two. We're aware that this is inconsistent and will try to resolve it ina future release.) |
|
|
|
|
Hi guys, I installed the May 11th build and my model would only open as an XML file. I could open it in the designer by right-clicking and selecting "Open with | Lightspeed Designer" (even though the designer was the default. The May 10th build worked fine for me in terms of opening a model, though. However, neither version has anything in the toolbox. I would add items manually, but i don't know where the DLLs are. Can anyone help? Thanks |
|
|
|
|
I opened up a model in the XML editor once on a 20100428 build and ever since the xml editor always opens instead of the designer. Even though the default is the Lightspeed Designer I just installed the 20100511 build and the problem is still the same. It may be a VS 2010 bug with file associations |
|
|
|
|
I've noticed that in VS2010 if you've opened a file with a non-default editor it can sometimes get "stuck" on that editor, even if you subsequently explicitly reopen the file with the right editor. This doesn't seem to be a LightSpeed issue: it seems to be a VS2010 issue. MiddleTommy, it sounds like this is your problem. If so, try opening the .csproj file in a text editor, find the XML element for the .lsmodel file, and delete the subelement <SubType>Designer</SubType>. Then try reloading the project in VS2010, reopening the file and see if it helps -- it worked for me but I make no promises...! Alex, it sounds like there may be a deeper issue with your installation, because you're not seeing anything in the toolbox either. (Or maybe that's just another symptom of VS2010 being confused about the right editor to use.) As a first step, could you try checking for a <SubType>Designer</SubType> element and deleting it as described above; if still no joy, could you try a full uninstall-reinstall and see if that helps? |
|
|
|
|
worked for me Thanks Ivan |
|
|
|
