how to correctly identify vs2008 version level? - asp.net-mvc

At SO, I searched "identify version visual studio" but failed to find an answer.
Scenario:
A generally accepted best practice is to install all service packs related to the software that one is using.
The applies to Visual Studio 2008 too. In some cases, it is absolutely essential, for example VS2008 SP1 is required if one wants to install ASP.NET MVC v1.0 RTM.
For most software, "Help, About ____" will reveal the version and often includes SP level.
With my VS2008, I get a lot of information, some of it is clear:
Microsoft .NET Framework
Verson 3.5 SP1
and some of it which is less clear:
Microsoft Visual Studio 2008
Version 9.0.30279.1 SP
The problem is that it is difficult to tell whether VS2008 SP1 has actually been installed.
The same information appears to be displayed in Help, About on computers that have vs2008 SP1 as well as those that have not been upgraded.
Likewise, different editions, example "Development" and "Professional" show the same results via Help, About.
--
QUESTION: how does one correctly identify her/his vs2008 version level?
edit: found this:
How do the .NET Framework, CLR and Visual Studio version numbers relate to each other?
I wish Microsoft would make this easier.
#nos ... your QFE is a hotfix ... http://en.wikipedia.org/wiki/QFE.
AFAIK, you've likely applied a security patch.
I guessing the "30279" part of 9.0.30279.nnnn means SP1 and the "nnnn" is a subsequent update level.
edit #2:
MORE INFORMATION
The challenge I find is to identify the version easily.
While this may seem strange, and while unfortunately
I lack a time machine, at least once I was certain that
I already had vs 2008 SP1 but ASP.NET MVC would not install.
At that time I applied the MS SP1 upgrade;
while executing, the upgrade said it was upgrading SP1 !!
After upgrading SP1 to itself, ASP.NET MVC did install.
Ergo, I find this so confusing. It would be so
much easier if Microsoft showed via Help, About, this instead:
Microsoft Visual Studio 2008
Version 9.0.30279.nnnn SP1
edit #3:
http://blogs.msdn.com/bharry/archive/2008/04/19/a-new-home-for-visual-studio-hotfixes.aspx
There are currently 169 hotixes:
http://code.msdn.microsoft.com/Project/ProjectDirectory.aspx?TagName=Hotfix
at least two to the hotfixes apply to vs2008 sp1:
http://code.msdn.microsoft.com/KB957912:
"KB957912 - Update for Visual Studio 2008 SP1 Debugging and Breakpoints"
http://code.msdn.microsoft.com/KB957507:
" KB957507 - Loc Intellisense to replace all Loc Int shipped with VS 2008 SP1"
"Please be aware [hotfixes may have
NOT] gone through full Microsoft
product regression testing nor has it
been tested in combination with other
Hotfixes."
UPDATE: on a windows 2008 web server R2,
I have Microsoft Visual Studio 2008 Version 9.0.30279.1 SP
which is "in theory" SP1 ~~ however, installing SQL 2008 Web Server
failed with the mysterious explanation that I required vs2008 SP1!!!
UPDATE CONTINUED: after applying the MSDN update to my
windows 2008 web server R2, I still have
Microsoft Visual Studio 2008 Version 9.0.30279.1 SP
which now really should be SP1 ~~ and I assume it must be
because the pre-install validation "rules" for SQL 2008 Web Server
passed and the SQL server installation then ran and completed successfully.

I have the same information. You're running Visual Studio 2008 SP1. This runs on top of .NET 3.5 SP1. Service Pack 1 for Visual Studio and .NET 3.5 is installed.

Well actually you can identify it with the given version. In your case the 9.0.30279.1 is really VS2008 SP1, it redistibutes Microsoft DLLs with this version (see C:\Windows\Winsxs for all of them).
So I suggest that you google for the version number. That should give you the correct VS2008 version.

Related

Visual Studio 2008 and 2005 accessing TFS 2008 source control?

We have a TFS 2008 server that we are using for source control having migrated away from VSS :D This is great for all our web projects as they can all be migrated to VS2008.
My problem is that VS2008 doesn't support development of SQL2005 SSIS packages.
It is possible to check SSIS packages into TFS2008 from VS2005? Would this conflict with the VS2008 install on the same workstation?
Thanks in advance....
Looks like you'll be fine if you install Team Explorer 2005 onto Visual Studio 2005.
Out of the box, Team Explorer 2005 works very well with most of the TFS 2008 capabilities. Work Item Tracking and Version Control function the same as they always had for TFS 2005. End users wouldn't even notice the difference, except in some rare cases the increased performance.
From : http://weblogs.asp.net/dmckinstry/archive/2007/08/27/considerations-on-using-tfs-2008-with-visual-studio-2005.aspx

How do I get MVC installed into Visual Studio 2008?

Does anyone have any basic instructions for setting up a first MVC project in Visual Studio 2008? I just installed Visual Studio 2008 and I am finding various instructions on how to set up the programming environment, but it's very complicated and there is no way to tell if the route I am taking is the best one.
If I want to start developing a MVC project, what do I need to do in order to get it going?
I am very confused by the "Web Client Guidance" instructions. For example, they don't say where to put the Microsoft.Web.Mvc.dll file.
Use Visual studio 2008 sp1 to get mvc installed...
Here is the download link
To get started With MVC
System Requirements
Supported Operating Systems: Windows Server 2003; Windows Server 2008; Windows Vista; Windows XP
.NET 3.5 SP1. Visual Studio 2008, Visual Studio 2008 SP1 or Visual Web Developer 2008 SP1 are required to use certain parts of this feature.
The official Microsoft MVC links for Visual Studio 2008 now seem to be dead.
To get this working on my old Vista laptop (with Visual Studio 2008) in 2013, I did this:
- Upgraded to Visual Studio SP1
- Followed this link to download and install "AspNetMVCRC-setup.msi" (1.74 MB):
http://go.microsoft.com/fwlink/?LinkID=141184&clcid=0x409
Once that was in place, my old Visual Studio let me create "Web | ASP.NET MVC Web Application" projects. Took about an hour and a half from end-to-end.
All I did was install the MVC installer and I opened their example app and it worked.\
MVC Installer
First of all, you need to download MVC from here.
After that, proceed with the installation.
You might want to refer to the tutorial for starters.

Is it possible to develop ASP.NET MVC with MS Visual C# 2008 Express Edition and IIS?

Is it possible to develop ASP.NET MVC with MS Visual C# 2008 Express Edition and IIS?
The tutorial states that 'Visual Studio 2008 or Visual Web Developer 2008 Express' are required.
You can't develop an ASP.NET (MVC or otherwise) using Visual C# 2008 Express without a big kludge. C# Express is mainly for Windows applications.
What you can do is download and install Visual Web Developer 2008 Express. This edition is for ASP.NET developer (in C# or VB.NET). Unlike the Standard or Professional, with Express the functionality is split into 4 seperate packages - C# Express for C# desktop development, VB.NET Express for VB.NET desktop development, C++ Express for C++ desktop development, and Web Developer Express for any type of ASP.NET development. You can download and install all 4 of these on the same machine (they should even share the same copy of MSDN Express).
If you want it all in one IDE, you need to pay for Standard or Professional.
Oh, and just make sure you download the SP1 version of Web Developer 2008 Express, it's really annoying trying to install SP1 on the Express editions (or at least it is if you have some other versions of VS on the same machine), and you need SP1 to install MVC.
It's definitely possible. I haven't really used the Express editions enough to know what is easier or more difficult in one edition or another but the Web Developer edition is also free.
An easy way to do this is to get the Web Platform Installer. It installs everything you need to get going with web dev. Some have claimed that its vista only, but I was able to use it to install it on XP HOME on my asus netbook.
Yes. I have installed some of the previews. You just don't get MS Test.
Edit: That was with VS Express Web Developer Edition, however.
What do you mean regarding running ASP.NET MVC projects? To run it, you'd need a Web server rather than Visual Studio. For development, you can develop a class library in C# Express that will be used in an ASP.MVC app but project templates are only available for Web development product line (Visual Web Developer or full VS)
Update to reflect OP edit: To develop apps effectively, you'll need Visual Web Dev or VS. There's no point in not using VWD Express as it's free.
At least Visual Web Developer 2008 Express Edition SP1 requred. I think it's just enough for ASP.NET MVC development if you are not working in the team. There are a lot of great 3d-party testing frameworks - you are not constrained only to MS Test.

Cannot add Entity Data Model in Visual Studio

I am running Visual Studio 08 Team Edition with .NET Framework 3.5 SP1 on WinXP. I am trying to add a Entity Data Model to my project, however, the option to add an "ADO.NET Entity Data Model" selection does not appear. To give you a visual, I am essentially following the directions here, but cannot get past step 5 (Right click on project and click Add New Item) because the option to add an EDM does not appear.
Any ideas? I'm sure I have all of the prerequisites.
I'm guessing that your VS 2008 SP1 installation did not complete successfully. Here are some things to verify:
Take a look at http://download.microsoft.com/download/A/2/8/A2807F78-C861-4B66-9B31-9205C3F22252/VS2008SP1Readme.htm and verify if any of the known issues apply in your scenario
Open a Visual Studio 2008 SP1 command prompt and type: devenv.exe /setup [ENTER]
Repair VS 2008 SP1 from "Add/Remove Programs" or try uninstalling and reinstalling VS 2008 SP1
Can you verify that you have:
Microsoft® Visual Studio Team System 2008 Database Edition GDR R2
The important thing to note is the GDR. Basically, it's like a service pack. They added some features, like Entity framework.
non-R2 would be ok too. the article you linked above doesn't list this at all, but it's required for entity framework
Here is a blog post about the issue.
Essentially, installing VS2008 SP1 (even if the about box on your installation can claim it's already SP1) resolved the issue for me.
Download page for SP1 here.
I was having the same issue as described here with VS2012. I have now installed VS2012 update 2 and this has resolved the issue, so if any one else stumbles upon this for VS2012, try that to fix the issue.

Basic Team Explorer usage questions

We are setting up a new TFS 2008 implementation as our first usage of TFS for source control. We have several projects in Visual Studio 2003, 2005 and 2008, as well as other script/non-Visual Studio based projects.
My question is, for the Visual Studio 2003 and 2005 projects do we have to install Team Explorer 2003/2005 and make use of them to add projects to source control and to check out/in files, or, can we just use Team Explorer 2008 to add projects and check in/out files? The thought being that the developer could use 2008 to check out any thing and then open the appropriate visual studio version to work on their local instance of the project before then checking it back in using team explorer 2008 within their local visual studio 2008 application.
The concern is that by using team explorer 2008, that visual studio 2008 might impose changes on the older systems solutions dll or control details.
Thanks for any guidance.
This is possible. I have colleagues who are using Team Explorer for non-code files (Word documents, help files, etc.) and use it like they would VSS or any other SCC.
As an added bonus, I'm pretty sure that TFS Server 2008 is backwards compatible to at least 2005 (haven't run against 2003 in awhile). IIRC, I've run VSTS 2005 For Developers against a 2008 TFS Server.
I would double-check for you, but I've recently recently re-imaged my dev machine and haven't re-installed 2005 (working on new stuff!).
As an aside, I've found TFS to be a huge timesaver as far as the whole dev process. The IDE integration is top notch, and the linked bug/task tracking and changesets, with alerts, notes, built-in queries and reports had me wondering how I ever got along w/o it.
HTH.
The Team Foundation Client for VS 2005 and VS 2008 can be installed side by side so there's no issue there (there isn't one for VS 2003, but you could probably use the MSSCCI provider).
You can however, if you want to, do all of your source control operations in VS 2008 (or the Windows Explorer extensions in the latest power tools) but work on the projects from VS 2003/2005 without any issues. You just need to make sure you don't accidentally open the project files from within VS 2008 because that will upgrade the project format.

Resources