I have Sharepoint 2007, and I am going to buy Visual Studio for the first time.
Does Visual Studio 2010 work with Sharepoint 2007?
Yes of course it does. But be aware of the different versions of Visual Studio.
VS 2010 you can build workflows, list definitions, site definitions, web parts, etc. etc.
You can't buy Visual Studio 2010 yet. It's not due to be released until this spring.
Related
I am using Visual Studio 2005 to work with Sharepoint 2007. I need sharepoint extension (VSSExtension for VS 2005).Tried in google but dint get any download link.
Can anybody post the link here
Thanks in advance
I typed sharepoint extensions for visual studio 2005 into Google and the first result is:
Windows SharePoint Services 3.0 Tools: Visual Studio 2005 Extensions, Version 1.1
Tools for developing custom SharePoint applications: Visual Studio project templates for Web Parts, site definitions, and list definitions; and a stand-alone utility program, the SharePoint Solution Generator.
I am using microsoft visual web developer 2010 express edition.
i want to create windows service but, the template is missing .
how can i install this missing template.
thanks and regards
Mohit Leekha
This is listed as a limitation within the Express Edition of Visual Studio 2010. I'm sure you can do something not so ethical to get around it to build a template, you can google for that one.
Now, you can build a windows service without the template, you just will not have all of the fancy design time support for a few items.
You should use Visual Basic (or C#) 2010 Express, not the Web version to build a Windows Service.
I made a template for Visual Studio 2010 Express you can get it at my blog: http://blog.larmib.com/2011/windows-service-template-for-visual-studio-2010-express/ it is for Visual Basic.
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
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.
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.