Fernando has previewed Visual Studio 2005 Codename “Whidbey” Enterprise Developer Edition Alpha. Below is an excerpt: ” Visual SourceSafe is a viable solution that lets you effectively manage project files. It tracks and stores changes to a file so that developers can review a file’s history, return to earlier versions of the file and develop programs concurrently.“
Visual Studio 2005 “Whidbey” Enterprise Dev Edition Alpha Preview
2004-07-08 General Development 20 Comments
This looks like a huge step forward for Win development to me… Now if only REBOL/View could get a good IDE
How much new patents (pending) on this one?
I am currently using the most recent Beta version of VS.Net 2005 and it is still a little rough around the edges gut definitly a big improvement in functionality over 2003. This article seems to only be using the Alpha version, which they have made many improvements since then.
Review seems to be full of typos, pop-up ads and is spread over multiple pages due to the huge number of ads on each page.
Waste of time.
Hahahahahahahah…. “Visual SourceSafe is a viable solution…”
They left off the “… if your development group is stupid enough to keep using VSS instead of moving to CVS, Subversion, Perforce, etc., etc.” part.
Did anyone new to VS with the .NET releases actually miss SourceSafe?
With VS 2005, you finally get the these controls in your Windows.Forms: “MaskedTextBox edit control, the Sound Player control, the Web Browser control”. That is unless you use VB 6.0 COM objects or purchase third-party controls. Imagine that: the third generation of .Net development is finally catching up to VB 6.0.
Before .NET I hated every ms development environment and stuck with Borland or Java. But now everything they do impresses me. Visual Studio is a joy to work with, as is C#.
The only thing they lack is native compilation. Since .Net is designed as a one-platform environment, that lack is ridiculous. WE WANT A LINKER!
FYI: the website has no problems with Opera 7.52
Looks good with Links too.
Looks the same in IE and Firefox. What a troll.
Anyone know when this beast is supposed to come out?
Hehe, yeah, I thought quite about the same thing.
VSS really sucks and I’m glad the team I work with at my company finally implements their workflow in Rational ClearQuest. *hoping*
Having used several different revision control systems I have to say that Visual SourceSafe is by far the worst. I personally recommend any one/two person teams to use Perforce, and above that see if you can bug management for the dosh as it is well worth it. Failing that, try SVN. Failing that, CVS. But just not VSS!
“Before .NET I hated every ms development environment and stuck with Borland or Java. But now everything they do impresses me. Visual Studio is a joy to work with, as is C#. ”
I think I once read somewhere that the user interface of Visual Studio .net is designed by some Borland people.
Perforce is by far the easiest to get setup and manage, and from the end user point of view it has CVS and Subversion beat hands down.
You can setup a 2 user server for free, which is very nice for personal use.
i wouldn’t be surprised if it’s as early as Q4, the beta 1 release is pretty solid for a beta and is nearly feature complete (from what i can tell via my own meanderings with it). 6 months is probably a relatively reasonable timeframe to expect it though. btw, the installation of beta 1 is a snap and plays very nicely with all other versions of .Net (and finally ships with a version switcher for asp.net built right in).
No one can make such good tools like Microsoft. They have the most elite coders who can write really good code. Microsoft invented “code complete” a power technology that does not exist on Linux or Mac.
I love Microsoft. They are my idol. One day I will build massive application using Microsoft. They are my friend. I love Microsoft development tools.
Aside from the article being a complete waste of time this is an tech preview from March! There was a second in May and at the moment there is the Beta 1 release of Visual Studio .NET 2005 and the various Express products – http://msdn.microsoft.com/vstudio/
There is nothing to see here – please move along. (or go to neowin.net to see more interesting news from Microsoft)
You have native compilation. It’s called NGEN.EXE. 🙂
NGEN still requires that the original CIL assemblies be present. There is no avoiding this, as large portions of .NET functionality are dependent upon IL. For example, Reflection requires IL, not native code, and Remoting, Web Services, Serialization, and more all depend on Reflection.
Furthermore, while .NET is targed for One Platform (Windows), it isn’t One Hardware Platform. There’s AMD vs. Intel, which can impact code generation and optimizations (SSE vs. 3DNow!, though this may not be taken advantage of now), 64-bit platforms (x86-64 and Itanium), and the Windows CE platforms (MIPS, ARM, etc.). .NET permits deployment of a single assembly across all these hardware platforms; staying entirely with native compilation would prevent this.
Finally, there’s the Linker request. A linker doesn’t require native compilation. It just requires additional functionality, merging of assemblies into a single file, etc., some of which could be possible now (with the appropriate tools) and no changes to .NET. However, a linker introduces its own problems, particularly with security. It’s very similar to private vs. shared assemblies. If the assembly with a security issue is shared (in the GAC), you can update it once and all apps are fixed. If the assembly is a private assembly, then all apps which use the assembly must be individually updated. The same thing would be required with a “statically linked” program: all programs which use the insecure assembly would need to be updated. This can be an administrative nightmare.
See also: http://blogs.msdn.com/jasonz/archive/2004/01/31/65653.aspx.
A good example of security issues with bundling/embedding/linking would be MSDE, Microsoft’s embedded SQL Server. There have been a number of security issues found in MSDE over the years, and a number of apps use it, but haven’t been updated to use the bug-fixed versions. Often, people will be using it without knowing they’re using it, as it’s embedded within another application. See the NTBugtraq archives for examples and http://www.sqlsecurity.com. Certainly the developers of these apps should track the MSDE bugs and issue product updates when appropriate, but many don’t. Even Microsoft has been known to ship known-bad MSDE versions with new products (http://www.ntbugtraq.com/default.asp?pid=36&sid=1&A2=ind0306&L=NTBU…).