Visual Studio 2013 is now available for MSDN subscribers! Public launch is Nov. 17-http://events.visualstudio.com/
What’s new in VS 2013 : http://msdn.microsoft.com/library/bb386063(v=vs.120).aspx
For developers and development teams, Visual Studio 2013 easily delivers applications across all Microsoft devices, cloud, desktop, server and game console platforms by providing a consistent development experience, hybrid collaboration options, and state-of-the-art tools, services, and resources.
Below are just a few of the highlights in this release:
||Innovative features for greater developer productivity: Visual Studio 2013 includes many user interface improvements; there are more than 400 modified icons with greater differentiation and increased use of color, a redesigned Start page, and other design changes.
||Support for Windows 8.1 app development: Visual Studio 2013 provides the ideal toolset for building modern applications that leverage the next wave in Windows platform innovation (Windows 8.1), while supporting devices and services across all Microsoft platforms. Support for Windows Store app development in Windows 8.1 includes updates to the tools, controls and templates, new Coded UI test support for XAML apps, UI Responsiveness Analyzer and Energy Consumption profiler for XAML & HTML apps, enhanced memory profiling tools for HTML apps, and improved integration with the Windows Store.
||Web development advances: Creating websites or services on the Microsoft platform provides you with many options, including ASP.NET WebForms, ASP.NET MVC, WCF or Web API services, and more. Previously, working with each of these approaches meant working with separate project types and tooling isolated to that project’s capabilities. The One ASP.NET vision unifies your web project experience in Visual Studio 2013 so that you can create ASP.NET web applications using your preference of ASP.NET component frameworks in a single project. Now you can mix and match the right tools for the job within your web projects, giving you increased flexibility and productivity.
We also want to let you know that Visual Studio 2013 is no longer embedding the product key in the bits found on Subscriber Downloads. Once you launch the product, you can simply sign in with the Microsoft account associated with your MSDN subscription and your IDE will automatically activate. An added benefit of signing in to Visual Studio is that your IDE settings will sync across devices, and you can connect to online developer services. If you’d rather enter a product key, then simply bypass signing in and enter the product key found on Subscriber Downloads by selecting Register Product under the Help menu.
Download Visual Studio 2013 today and use the software, services, and benefits of your MSDN subscription to achieve your software development goals with greater ease and agility.
Lastly, please save the date for the Visual Studio 2013 Launch on November 13th as you’re cordially invited to join us online from virtually anywhere using your PC or mobile device. Watch the keynote live and see how developers like you are achieving their goals today with Visual Studio 2013. Then watch a comprehensive collection of expert product demonstrations from the Visual Studio development team in on-demand sessions.
Team Foundation Service is the new managed, cloud-based version of Team Foundation Server. Firstly, a little introduction to uninitiated:
Accessible from anywhere, using existing and familiar tools.
Plan projects, collaborate with your team, and manage your code online from anywhere.
Check your code directly into the cloud using Visual Studio or Eclipse. Manage work items and bugs in Internet Explorer, Chrome, or Safari.
Get started quickly, with no infrastructure to manage.
Go from “Sign up” to first project in minutes, and set up a Continuous Integration (CI) build in a few easy steps.
Your source code and work items are stored in the cloud, making server configuration a thing of the past.
All languages and platforms welcome.
From C# to Python, from Windows to Android, you can use a variety of languages and target a variety of platforms.
Whether you’re a team using Microsoft tools, or a freelancer targeting Android with Eclipse, our services help you focus on what you do best – building great apps.
While the help sections are pretty decent, I found that connecting via the web interface didn’t seem to want to work for me due to an authorization error, so I went with the old-school approach of connecting via creating a TFS Server connection in Visual Studio directly.
Note: If you are connecting from Visual Studio 2010 you will need to first install the Visual Studio 2010 SP1 Team Foundation Server 2010 Compatibility GDR.
Here is how (assuming you got past the simple signup process) you set up a basic connection from the Visual Studio UI to Team Foundation Service:
1. Open up Visual Studio 2012, and open the Team Explorer panelbar:
2. Click “Connect” under Team Foundation Service, and then on popup dialog click “Servers..”:
3. Click the HTTPS radio button first, then type in <your server name>.visualstudio.com into the Name or URL of Team Foundation Server input:
4. Select the new Team Foundation Service Server in the Connect to Team Foundation Server dropdown:
5. That’s it! Your source code is now on cruise control, no more conversations with your local IT guys about the merits of “what’s this TFS server and do you still need it?” 😉
The Community Kit for SharePoint: Development Tools Edition extends the Visual Studio 2010 SharePoint project system with advanced templates and tools. Using these extensions you will be able to find relevant information from your SharePoint environments without leaving Visual Studio. You will have greater productivity while developing SharePoint components and you will have greater deployment capabilities on your local SharePoint installation.
This version is targeted for users running SharePoint Foundation 2010, for the server version go here.
This project provides extensions to four core areas; Environment, Exploration, Content and Deployment.
Enhancements to the Visual Studio environment include the new SharePoint References tab available on the Add Reference dialog, allowing you to easily reference any SharePoint assembly without searching the file system or GAC for it.
Exploration extends the new SharePoint Explorer with advanced information about SharePoint sites such as the installed Web Parts and Master Pages or the Feature dependencies and elements. Also included in the Explorer are a variety of import functions to bring existing SharePoint items into your active solution.
The Content area includes advanced templates such as Linq to SharePoint, Custom Action or Delegate Control. Become extra productive while developing sandboxed solutions using the SharePoint Full Trust Proxy. Utilise the SharePoint Console Application project template to quickly build SharePoint code.
Our enhanced Deployment functions give you the ability to utilise quick deployment and almost a dozen other productivity enhancing deployment steps, including automated deployment (per file on change deployment).
Find the complete overview of all the CKS Development Tools Edition features on the documentation tab of the project site. The CKS Development Tools Edition works with Microsoft’s Visual Studio 2010 SharePoint Power Tools.
What’s new in this release
The current 2.3 release includes the following features:
– Activate Quick Deploy from global shortcuts – Activating the shortcut keys now from any VS item not just the SP Project.
– New ASHX SPI – New ASHX handler project item template.
– Cancel Adding SPIs – Cancel adding SPIs feature which stops VS automatically adding a SPI to features.
– Updates for Quick Deployment steps – Correct processing of the assembly name.
– Quick Deploy GUID replacable params – Quick deploy now supports GUID based replaceable params and will represent the latest dll version of them.
– Quick Deploy fixes – Improvements to Quick Deploy. Read only files not locked during Quick Deploy.
– WCF SPI Template update – Changes to the SPI to deploy to the root of the ISAPI folder to remove the need for a custom web.config. This should make deployment simple for default WCF SPI’s while still allowing custom implementation with a sub folder and web.config to be done.
If you have a great idea for a deployment tool, template or any other thing that you believe increases developer productivity, contribute! Contact the Project team or add your idea to the discussion forum. Use the #CKSDev tag to follow and connect with the team on Twitter.
About the Community Kit for SharePoint
The Community Kit for SharePoint is a set of editions, components, tools and recommended documentation for SharePoint development. You are currently viewing the edition project site for the Development Tools Edition. To learn about the other editions and components you can go to http://www.communitykitforsharepoint.org/default.aspx.
So you plunk in a name for a new Team Foundation project in Visual Studio’s team explorer, and at some point thereafter have a requirement to change the name of the project.
Short and long of it- as far as my look-see has taken me, you can’t: https://connect.microsoft.com/VisualStudio/feedback/details/554539/cant-rename-a-team-project-in-tfs-2010
You can however delete and start from scratch:
- Open the Visual Studio 2010 Command Prompt window (found under Start > All Programs > Microsoft Visual Studio 2010 > Visual Studio Tools )
- Run the TFSDeleteProject utility using the following command line. TFSDeleteProject /Collection:<Collection Name> <YourTeamProjectName>
- Confirm delete by pressing Y and then press ENTER.
Full syntax is as follows:
Usage: TfsDeleteProject [/q] [/force] [/excludewss] /collection:<url> <team project name>
Deletes the Team Project from Team Foundation. To use this command, you must bea member of either the Team Foundation Server Administrators group or a member of the Project Administrators group for the project you are deleting. Use this command with caution because after deleting the team project it cannot be recovered.
[/q] – Do not prompt for confirmation.
[/force] – Continue even if some data cannot be deleted.
[/excludewss] – Exclude the project’s SharePoint site when deleting the project. This option will leave site intact so that it remains for other projects that may be using it.
/collection:<url> – The url for a Team Project Collection.
<team project name> – The name of the project. Use quotes if there are spacesin the name.