I know NAnt sees frequent use (well, I always use it for my CI builds) but there has been no new official release since December 2007. Is the project receiving active development any more or is it dead-pooled? It worries me that if I carry on using it, and it stops tracking the latest version of .NET, I'll eventually be left with a massive job when it comes to upgrading systems to a version of the framework that it can't build.
Has everyone else gone over to some other tool like MSBuild these days?
It seems as if development will be more active in the near future. This is from a message from the developers mailing list from 05 Mar 2010:
since we are in an early stage of
getting drive on nant again, I want to
ask if we could moving away from CVS.
My first proposal is to switch to
subversion.
...
I'm also using NAnt for quite some time, and while I was a little bit concerned about the project being dead, so far NAnt did its job very well.
Update: NAnt 0.90 Beta 1 was released on April 17, 2010
See the official blog - NAnt’s not dead, it was just resting
https://sourceforge.net/apps/wordpress/nant/2010/04/05/nants-not-dead-it-was-just-resting/
Related
My employer currently has access to a singular InstallShield 2016 Professional key. They're looking at upgrading to 2018 Premier and getting a second license, but want me to test out 2018 Premier by working with our actual installer. All of our installer files are checked into version control with the rest of our project.
According to Flexera's documentation, an evaluation copy of InstallShield implements a time limit for running setups produced by it. Makes sense - they don't want you creating your installer in the 21 day limit and then never buying the product.
If I'm careful not to implement anything specific to 2018 or Premier, will checking in anything I create and having it re-built on the machine with the full license avoid triggering this restriction? There are concerns that using the evaluation copy of 2018 Premier in an actual working environment will ruin what's already checked into version control and implement a five-day limit for our installer.
Note: We do plan on using the evaluation copy only as an evaluation. The trial period will be to determine how much more efficient it is to have two devs working on the installer, as well as to figure out if upgrading to Premier is worth the cost. We may or may not end up purchasing a second license at the end of the trial.
The expiration is built based on either the project requesting it, or the use of an evaluation copy of InstallShield for the build. So merely opening and saving the project with an evaluation copy will not mark a project as an evaluation. Nor will making and saving changes.
However, opening and saving a project in a newer version of InstallShield will upgrade the project, rendering it unusable (and thus unbuildable) in the older version of InstallShield. The Professional and Premier editions of the same version are generally compatible, but opening a project in the Professional edition may disable various features that were enabled in the Premier edition, even if you don't attempt to alter them.
Source control should make it easy to undo any project changes that interfere with your builds.
we are migrating from TFS 2010 to Visual Studio Online. Our biggest Team Proyect has 14k ChangeSets. We are trying to migrate but based on the current "speed" it would take about 18 days to migrate.
I now there is a similar thread but:
Slow TFS migration from on-premise to TFS online with OpsHub tool
but it does not provide a solution. So I'm asking for help.
For TFS 2010 we have one Application Tier Server, a Database Tier Server.
Both Servers are performing ok (Memory, CPU,Network) during the migration
We are launching the migration Utility from a differect computer which also has ok performace (Memory, CPU, Network)
But in 12 hours, only 400 changesets has been migrated.
We are using version 1.0.1.008
Thanks in advance
Update from OpsHub.
We have done major performance improvements in the current release.
It would be available to public by the end of this week.
Thank you Christian for your assistance in this case.
A rule of thumb is that it will take as long to migrate your history as it took to make it in the first place and those times are not outside the bounds of reality. I would ditch the history and move just the tip.
Clarification: No that is not slow that's just how long it takes to do migrations.
If you have a lot of modifications to code and or work items then it will take a very long time. You can make things faster by throwing processor at your source server and sticking a fat pipe in the way, but you are network bound.
You could spin up an Azure server in the same data center as your target VSO and install and configure your TFS 2010 environment there. Then run the migration. That will be much faster, and will still take a long time.
HI, In mongodb site there are two setups available in production release.So what is nightly whats the difference between 1.6.5 and nightly?
I would expect the 1.6.5 one is the official build release for that version. The nightly build is most likely the nightly build for that branch of development.
If there was a bug (security issue, whatever) which was discovered in 1.6.5, it would likely be fixed (over however many days it might take), at which point the fix (which may or may not be feature-complete) would appear in the nightlies, but not yet in the final release above it. When they were happy it was ready for release, there would be a new release from the 1.6 branch (most likely 1.6.6) and the cycle would continue until the 1.8 branch (which is currently 1.7) replaced 1.6 as the stable GA branch. MongoDB's version numbering strategy is explained here.
I hope that makes sense, and I believe that would most likely be what happens. Of course, if anyone is involved in MongoDB's development and wishes to correct me, feel free. :)
I used Business Desktop Deployment (BDD) to build my project. Scripts are written in python. The BDD I am having doesn't support Visual Studio 2008.
Please tell me what is the latest version of BDD which supports VS2008
where I can get more info about Business Desktop Deployment?
BDD is a mini-methodology related to acceptance testing and TDD (it does stuff higher up, but this is probably what you're doing).
From your question, it looks like you've been writing BDD scenarios or unit examples in Python. Visual Studio isn't a great tool for writing Python in. If you want to carry on in Python, try Vim, or you might be able to get a Python plugin for Eclipse or IntelliJ.
If you want to use Visual Studio to program, use C# or F#. There are a couple of great BDD frameworks - SpecFlow or TickSpec - which can help you.
More information, including a list of tools, is available on the Wikipedia page on BDD.
Otherwise, please clarify your problem. It doesn't make huge sense in its current form!
Edit: Well, I learn something new every day. BDD also stands for "Business Desktop Deployment", and is a Microsoft product. Here's a page with an update suggesting you should use Microsoft Development Toolkit. Hope that points you in the right direction. I imagine the tool we've been using, click-once, does something similar.
You should probably know that few people seem to recognise BDD as meaning anything other than Behaviour Driven Development in software these days. I've heard Binary Decision Diagram as well; not often though. Good luck in your search.
There's an article here that might help you with Business Desktop Deployment (BDD) versions. It's dated March 2009 and says:
Microsoft Deployment Toolkit 2008 Update 1 replaces all prior versions of MDT and BDD. It provides additional support for new OS versions and deployment scenarios and is the upgrade path for users of earlier versions.
The article points to the MDT 2010 download page.
Does no such plugin exist?
So to be clear, I realize that RedGate has their own SSMS SCC app, and I realize that VSS2k5 will integrate in. I'm looking to stay with Hg as that's where my source already is, and I'ld like to find something that my team can stay consistent with on their tools.
As is, I guess I'm going to have to just run it through TortoiseHg and a folder with manual maintenance. Which isn't terrible, but naturally it would be nicer if there was an app pre-existing that I could consume.
And no, I don't have the time or inclination to write one myself. Not before Summer 2011.
Thoughts or ideas?
There are two versions of HgScc plugin:
HgScc - uses old MS SCCI API, works with MS VS2005/2008/2010 and with some third party IDEs. Last version of this plugin was released in 2008. It is not actively developed anymore, because MS SCCI API is very limiting and does not allow a tight integration with Visual Studio.
HgSccPackage - uses MS SCC Package, works only with MS VS2008/2010. This version of plugin currently in active development.
To get the first version of HgScc follow the instructions here:
MSSCCI compliant Mercurial client
Red Gate SQL Source Control is looking into supporting Mercurial in a future version, http://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/803713-mercurial-support-as-source-control-system.
SQL Server 2012 (Denali) is using the Visual Studio 2010 Shell as the basis for the new Management Studio. I haven't tried it yet but I am hoping that tools such as VisualHg will work in Sql Server 2012. I will update this post after I get on my laptop that has the 2012 SQL Management Studio installed.
Have you tried hgscc? I know it integrates with Visual Studio, but I haven't tried it with SSM