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
|
so you must have known this would be coming at some point... :) i've got a powershell script i use to update a lightspeed nuget package which I have created and host locally. script:
then it's easy to update LS to the latest nightly build in all my solutions. have you considered hosting nightly builds in your own nuget server (would obviously have to be a secure atom feed)? cheers |
|
|
[quote user="Justin"]so you must have known this would be coming at some point... :)[/quote] We sure did. *grin* I've not figured out NuGet clearly enough to be sure what we can do with it and what we can't. It doesn't seem to provide a way of running a MSI, only of updating DLLs and running PowerShell scripts. Is your local store just serving up the DLLs, or is it also updating the designer and everything? If the former, how does it help (since you're having to run the MSI anyway)? Is it that it fans out the DLLs to all your project Lib directories? (Or you don't even need Lib directories, your projects just reference the package?) We're certainly interested in providing a service like this and if you can share any details of how you're setting things up and (especially) what the NuGet feed is doing for you, we'd be very interested to know so that we can scope our efforts a bit! Thanks! |
|
|
yes, the main benefit for me is that i can easily fan out LS upgrades for all the projects in my solution(s). each solution contains its own LS assemblies under the standard nuget packages dir - ie there are no references to the GAC or LightSpeed installed bin dir. We need this because each solution has to carry its own dependencies onto the build server. And that way I can update a solution without having to worry about other solutions - they can all run their own versions of LS. As long as the designer doesn't break backwards compat - which I presume it won't ever!
stream of consciousness: to be honest, i had forgotten when i wrote the post that nightly builds also require LS uninstall/reinstalls. I'm guessing that usually people are interested in nightly builds when the designer is updated - can't be too often that someone desperately requires a bugfix in the core LS assemblies...? So regular nightly builds are probably only useful if the designer is updated too - which will require an uninstall/reinstall - which is way outside the purview of nuget. so what i think would be most useful would be a script (powershell or whatever) which does the four steps i mentioned. Once the uninstall/reinstall has happened, then one wants the new LS assemblies available on a nuget server/location somewhere. But when you use nuget to upgrade the LS assemblies in each project you absolutely must ensure you get the LS assemblies that are the same version as just installed, else you'll get horrible nightly version mismatching. So perhaps mindscape could host a public nuget server with the latest nightly builds. They won't be useful unless someone has already run a script (which mindscape could possibly provide) to uninstall/getlatestnightlyviasecurefeed/install.
As long as the currently installed VS designer is always same or newer version than the LS assemblies any given project references, there shouldn't be any problems. sorry, that was a bit longwinded.
my existing nuget packaging script fwiw: param(
and the assoc nuspec file: <package> |
|
|
Is there any news on this? The lack of NuGet packages is becoming too clear in the development process. Even if you can't run the installer (I think PostSharp does?, they have NuGet packages), NuGet packages would be great just to be able to atleast update the whole solution. Currently I have my own NuGet packages just to make this more manageable but I think that in this age of NuGet, Lightspeed will become more accessible in the general sense, and also easier to try out. If NuGet will not allow the required installer, what about a MS Visual Studio extension, would this give options like with the Web workbench? I am curious what the plans are on this front. Cheers! |
|
|
Do nightly builds require an uninstall? I assumed the installer would either deal with it or let me know if something went awry. |
|
|
We are having a look into this, but the limitations with both with NuGet and the VSIX installers around what you can install/hook into means that we cant properly run our MSI installer (which we need to do to set up custom tools and the like), so we are thinking NuGet for updated runtime assemblies would be the extent of this. At this stage I am hoping we can get this set up to co-incide with the next major version for LightSpeed (5.0) which we are currently working on. The MSI installer will uninstall previous versions, although I personally always uninstall manually as an old habit :)
|
|
|
since i originally started this thread i can now tell you that it's actually the opposite of what i said. most times I don't care about upgrading the designer from nightly builds. |
|
|
hi again, fwiw, and while you're thinking about nuget support for v5/nightly builds, i noticed this - might have some useful ideas for you: http://aspnetwebstack.codeplex.com/discussions/353867 if you were to do something similar, it would be great if you did implement the pre-release versioning for assemblies. and if you're able to create an secure nuget feed (for those who have purchased the source code license), would be triple awesome if you could provide non-obfuscated nightly build nuget packages. |
|