Working on a company using the .Net Framework 2 (vb6 and vb.net 2005) and a very rudimentary sourceforge setup, I'm kindof at a loss when I was tasked to "...find a suitable Open Source Unit Testing & Bug Tracking system..." for the team. Those were my superior's exact words.
I know about the Team Foundation Server's capabilities, but the company doesn't want to adopt it and instead go for an open source solution. Any ideas on the best system which are compatible with the code used by the dev. team?
We too are using the .NET Framework 2 (VB.NET 2005) and have begun unit testing with the NUnit unit-testing framework (since our client is unwilling to pay for TFS, etc.)
You can find out more information here:
http://www.nunit.org/
Hope that helps,
Jeff
Related
I have started writing tests for my project and am stuck at a point where my one object is dependant on another object. The test Framework I am using is MSTEST and I am using .Net 3.5 with visual Studio version 2008.
I would really appreciate, if you can share the best practices using this framework.
Also please let me know any better testing framework under the constraints mentioned above (it should be free to use).
Read up on Dependency Injection. It is a collection of code patterns that allow easier unit testing. I have just finished reading 'Dependency Injection in .NET' by Mark Seemann and it covers this problem in great depth. I would recommend it strongly.
I have a Compact Framework 2.0 application written years ago in VB.NET using VS2005. The application uses a local SQL compact database (.sdf) file. The application has been running on HP iPAQs for years.
I want to look at making this available to Windows Phone users. Any suggestions for the easiest way to do this? When I say easy I mean quick I suppose, the client is not interested in paying for it, so if there was a crude way to implement/achieve it I would be prepared to go that route.
The alternative is building a new Windows Phone app, my first. Which would be fun, but not very good for the balance sheet! Thanks all.
Probably the only option available is going to be a wholesale rewrite of the application. If you were strategic in your original design and kept the business logic and UI separate, then that code will transfer pretty easily, but the data access code will have to be rewritten and all of the UI code will have to be rewritten.
Does anyone have any good resources for working with the TFS 2010 API? I specifically looking at how to create, read, update and delete work items.
Please see the Team Foundation Server 2010 SDK on MSDN Code Gallery. More content will be coming on-line for the RTM release, but you should find enough there to get you started. Contact me know if you have any questions.
Shai Ratan's blog has a huge wealth of examples. They're 2008 but 99% still relevant.
www.tfsexamples.com has 2008 examples, but still relevant
WorkItemManager class from a TFS OS project I'm currently working on called Spruce, which is ASP.NET MVC 3 front end for TFS workitems. The class illustrates a large portion of what you need, although no deleting examples. WorkItemSummary in that class is simply a scaled down WorkItem object.
BacklogItemHandler from the Scrum Dashboard project on codeplex also has a lot of good examples of how to use the API.
I heard from a friend that Microsoft rewrote all the Windows Workflow Foundation (WF) again and changed everything was in .Net 3.5.
Is that true?
And what about what we learned about WF in 3.0 and 3.5?
According to this article:
http://visualstudiomagazine.com/articles/2009/01/01/windows-workflow-changes-direction.aspx
Windows Workflow Foundation 4.0 is a "bottom-up rewrite with entirely new thinking...WF 3.0/3.5 will remain part of the framework and will run side by side with WF 4.0. This lets you manage the transition at a time that fits your organization's broader goals."
...which is code for, "We know we just screwed up your programming model, but we have a long term strategy, so we hope you will forgive us."
The article goes on to say that
The gains are enormous: custom
activities take center stage, and
authoring them is much simpler;
workflows are entirely declarative;
and there are three workflow flow
styles that you can combine
seamlessly. It's possible that you
could see a 10-fold improvement in the
time required to create and debug
workflows, in addition to 10- to
100-fold runtime performance
improvements.
The change is not without its detractors. In this article at DotNetKicks, the author states that "Microsoft is seriously damaging the Dot Net developer community and adoption in the industry with these half baked product releases and abrupt about-faces after shipping."
Which is why I generally wait for the 2.0 or 3.0 version of Microsoft technologies, although I made an exception for ASP.NET MVC.
We found the workflow product to be difficult to wrap your head around when it came time to pass data in and out. Scott Allen had a series of articles that did a good job describing the process, but still this was not at an easy task.
That's what the word on the street is. And on the internet. 3.0 and 3.5 will be deprecated, but still available.
Is this change not in Visual Studio 2010 beta 1? Download it, find out, and tell Microsoft what you think of it.
I know of Rational Rose and we have got Rational Rose 6.
But I am looking for some other tools which are more usable, which do not complain that they are not running in Windows 98/2000 (when installed and run in WinXP) and has got better features as compared to Rational Rose 6.
Check out Enterprise Architect. It's not expensive and does a lot of things well.
This lists Visual Basic (as distinct from VB.Net) as supported.
Enterprise Architect does reverse engineering and code generation for VB6
I did check out Enterprise Architect on SpareX's web site but could not find any reference stating that it handles reverse engineering or code generation for VB6.