Visual Studio

In SharePoint 2013 JavaScript is the new default language and all our (at least mine) solutions and projects are using JavaScript more and more, even though everything is not built as SharePoint Apps. Farm or Full-trust solutions built using JavaScript will in many situations create a better user interface and an improved perceived performance. The more we build user interfaces using JavaScript we cannot just forget about some of the basic UX rules, such as using localization.

Visual Studio 11 Developer Preview is now available for download für alles and it does not only include the Windows 8 stuff like the previous preview did - this one contains the thing we all want - the SharePoint Developer tools. Overall the performance of Visual Studio 11 is blazingly fast! I regret I tested it - since I will go back to 2010 tomorrow (or even tonight). They team has done a great job and included a lot of the PowerTools natively; such as the new Solution Explorer, the improved search feature etc.

The by far best utility for SharePoint 2010 developers is the CKSDev extension (Community Kit for SharePoint - Developer extensions). It’s an extension to Visual Studio 2010, available through the built-in Extension Manager. To install it, just hit Tools > Extension Manager and then search for “CKSDEV” in the Online Gallery. Version 2.0 of CKSDev was released yesterday, and if you already have it installed you should have been notified about the update.

The other day I had an interesting and great workshop with a customer about the BI features in SharePoint 2010. SharePoint Insights is one thing that really gets me going - so much great stuff can be unleashed using Excel, Visio and PerformancePoint Services. One thing that annoys me with the default settings in SharePoint 2010 is the BI Center. A BI Center does not support the “BI for everyone” mantra - that center only turns numbers and KPI fans on.

This is a follow-up post to the Understanding folders and namespaces in Visual Studio 2010 SharePoint Solutions, Packages and Features (probably my longest blog post title, except this one…). In that post I discussed how folders and namespaces are handled in Visual Studio 2010 SharePoint projects. I will continue to show some details and tips on how you can affect the outcome of your project/packages. Long feature folder names As the previous post showed the features generated by Visual Studio ends up as a subfolder in the {SharePoint Root}\TEMPLATE\FEATURES folder.

Yesterday Todd Bleeker (SharePoint MVP) wrote a post about the SharePoint Project SPI’s where he explains how SPI effectively are folders within a SharePoint solution. I thought that I should continue that discussion a bit and looking at how these folders and other things such as packages and features affects the actual deployed artifacts. Packages A package (#3 in the figure to the right) is the actual WSP file that will be created containing all your objects from your solution that will deployed to the SharePoint application servers.

Visual Studio 2010 LightSwitch is a new kid on the block in the Visual Studio suburbs. Basically it is a rich client application editor for Visual Studio that allows you to develop (or should I say “click-through”) an application very easy without any programming skills at all. You can create a custom database, attach to an external data source or WCF RIA service and last but not least hook it up to SharePoint.

As you know the usage of JavaScript has been more and more used in web applications over the past years for technologies such as AJAX. JavaScript can accomplish really cool stuff on the client side and make the user interface more interactive and responsive. Just take a look at SharePoint 2010 - that’s some heavy JavaScripts there (a bit to heavy IMHO). So lets assume that you are building some new cool stuff, in SharePoint of course, and why not a Page Component for a contextual Web Part.

If you have been working with SharePoint 2010 development using Visual Studio 2010 you have most certainly stumbled upon the new replaceable parameters that replaces data in your solution files during the packaging process. For instance Visual Studio uses $SharePoint.Project.AssemblyFullName$ in the Web Part control description (.webpart) files and this is replaced with the assembly full name (strong name) during packaging. By default it looks like this when you create a new Web Part:

I thought I should share my experience on working with SharePoint 2010 development on Windows 7. My previous posts on installing SharePoint 2007 on Vista and Windows 7 are posts that are quite popular. The downside with the “old” SharePoint version is that it was not officially supported to install it on a client machine, but SharePoint 2010 is supported for installation on Windows 7 and Windows Vista SP1 for development purposes.

The SharePoint 2010 Development Tools for Visual Studio 2010 is great and I really like the way that the project is built using the different artifacts. One thing really annoys me though and that is the way that the code is generated and named when you add items. For example if you create a project and then add a Web Part item to that project then Visual Studio will create a Web Part class with a namespace and class name like this:

Visual Web Parts are a nice addition for SharePoint 2010 developers. A Visual Web Part is essentially SmartPart revisited and is one of the project types of the new SharePoint extensions for Visual Studio 2010. Sandboxing is one of the most interesting features of SharePoint 2010, especially for large scale implementations and hosting providers. The Sandboxing feature, or User Code Solution, allows you to easily upload a SharePoint feature into your farm into a special controlled environment – called a Sandbox.

Windows 7 has an upgrade to Virtual PC which allows you to run Windows XP applications virtualized on your Windows 7, without having to run the whole desktop running. I still have to use Visual Studio 2003 to support some old good applications including SharePoint 2003 apps. So I have used a Windows XP virtual machine to run it, but now I can fire up Visual Studio 2003 directly from my Start menu in Windows 7.

Here is a tip for you Codeplex users out there. If you are using the Visual Studio and the Team Foundation source control then you are prompted for username and password every time you open up a project. This dialog does not contain any functionality to store the username and password. If you are often opening projects and/or switching projects entering usernames and passwords can get annoying. If you are using Windows Vista or Windows 7 you can store the usernames and passwords in a pretty secured way using the Credentials Manager.

A recent discussion about how the licenses of Windows, SQL and SharePoint Servers should be handled when we are developing solutions using Virtual Machines made me throw away a mail to Emma Explains Licensing. The concern was that; do we have to pay licenses for every VM or test server? That would have been insane! But I wanted to have this explained how this licensing works - a lot of you perhaps already know but I always have a hard time getting all the different licensing options and rules.

So the last day of PDC 2008 is over. The brain has been cooked for a few days… This very day did not have any keynote and I kicked off with a session on the Visual Studio Extensions for SharePoint. I have note used this add-in since the first releases of it since I didn’t like it that much but had instead relied on manual packaging and deployment as well as STSDev.

Microsoft has now released the final bits of Visual Studio 2008 Service Pack 1 and the .NET Framework 3.5 Service Pack 1, download here. A lot of stuff has been improved such as stability and performance, no need for me to repeat all this since you can find it a gazillion of blogs as well as in the Microsoft Knowledge Base. One improvement I did not read about is that they have fixed/updated the icon of the devenv.

I have repeatedly had Visual Studio 2008 hang or stop responding when I’m checking in files to Visual SourceSafe, especially when checking in large amount of files. It just stays there and eventually dims out (as non responding application does in Windows Vista). The ultimate solution is to kill the devenv.exe process and start over. But I have discovered that it is not just hanging, it’s just the main application window that stops responding.

Not only the Office clients and servers got patched yesterday, Microsoft also released an update to Visual SourceSafe 2005. The update contains a number of hotfixes which includes performance, usability and stability improvements, as well as improvements to compatibility with Windows Vista and Microsoft Visual Studio 2008. Download it here (KB943847)

Remote Debugging is a great feature to use, especially when you work with virtual machines. It allows you to develop and debug locally but have the code running on another machine, virtual or physical. Microsoft SharePoint can’t be installed on a Windows Vista or XP workstation, but needs to be installed on Windows Server 2003 or 2008, so the general recommendations has been for developers to have either Windows Server as their main OS or have a virtual machine with Windows Server.

Visual Studio 2008 is released and MSDN subscribers can download it, which I’m currently doing. .NET Framework 3.5 is also final and available for download. Bye bye Visual Studio 2005…

The news that Microsoft will be releasing the .NET 3.5 framework libraries source code for everyone. The code is under the Microsoft Reference License (MS-RL) which means that the code is available for you to use as a reference or for debugging, not to modify or extend (if you simplify it…a lot), i.e. it’s not open source. What’s in it for us? Scott Guthrie has all the goodies in his post, where he explains how this release of source code integrates into Visual Studio 2008, and how you can debug into (for example) the ASP.

Visual Studio 2005 has now been updated with full support for Windows Vista. It’s an update to Visual Studio 2005 Service Pack 1 and fixes a number of issues when running VS 2005 on Vista. If you have the beta of the update (KB929470) then uninstall it before installing the final update.

The SDK for Visual Studio 2005 has been released in it’s fourth version, download it here (124 Mb). The Visual Studio 2005 SDK 4.0 contains a number of new features and fixes, read more about them here. One of the interesting new features are the Package Load Analyzer which will help you troubleshoot your package load issues. The DSL tools contains a number of minor bugfixes mostly related to the designer.

Aaron Brethorst has published part two of his UAC and manifests series, this time he shows us how to embed the manifest into a managed application using Visual Studio 2005.

Here is a list of cheat sheets for the Windows and .NET platform that I frequently use and I think are of great interest. Visual Studio 2005 Keyboard Shortcut References Visual C# 2005 - PDF grayscale | PDF color Visual C++ 2005 - PDF grayscale | PDF color Visual Basic 2005 - PDF grayscale | PDF color SharePoint and Office stuff CSS Reference Chart for SharePoint 2007 (Microsoft Office SharePoint Server 2007 and Windows SharePoint Services v3) CSS Reference Chart for SharePoint 2003 New Office 2007 User Interface - Word | PDF Web and ASP.

As you probably already have read by now is that the XSLT 2.0 and XPath 2.0 are now W3C Recommendations. XSLT 2.0 is a really nice step forward in the XML transformation technology, a technique that we base our software on to enable us to produce content for different devices, platforms and targets. XPath 2.0 and XSLT 2.0, in specific, could help us making these transformations much easier without having to use XSLT Extension Objects for some tasks.

The Domain-Specific Languages for Visual Studio 2005 Redistributable Components are now available from Microsoft Downloads. You can now use the DSL designer in Visual Studio 2005 Standard (and above), sorry you can’t use these extensions in the Express versions, without having the complete Visual Studio 2005 SDK installed.

Today I start my two weeks vacation and I thought I should summarize this year. The year of 2006 has been characterized, for me, as the year of Betas and Technology Previews. I have been trying to involve myself as much as possible in the all the goodies flowing out of Redmond. Microsoft has released numerous amount of new applications and upgrades. Internet Explorer 7 The new version of Internet Explorer is the application this year that will have most impact in the short run on users.

Microsoft has now released the first Service Pack for Visual Studio 2005 and the Team Foundation Server. The Service Pack comes in several versions, depending on which version of Visual Studio 2005 you have. Here are the downloads: Visual Studio 2005 Team Suite SP1, this updates Standard, Professional and the Team Editions Visual Studio 2005 Team Foundation Server SP1 Visual Studio 2005 Express Editions SP1 What I look forward is that the Service Pack addresses theses issues:

The Architecture Journal, an online magazine by Microsoft with focus on software architecture, have posted two articles on Domain-Specific Languages, DSL. Domain-Specific Modeling A five page article on what Domain-Specific Languages and Modeling is about and when to use it. Bare Naked Languages or What Not to Model An seven page article on how DSL fits into the software factories methodology.

Aaron Brethorst, Program Manager for the Visual Studio - IDE team informed me about a new article on MSDN that explains the Visual Studio Support on Windows Vista. The FAQ contains good answers to the common questions on why there is no Visual Studio.NET 2003 support and how to run Visual Studio 2005 with elevated privileges. There are several questions and workarounds worth reading. I’m still considering wating for the non-beta version of the Visual Studio 2005 SP1 before migrating to Windows Vista.

The Microsoft.NET Framework 3.0, or just .NET 3.0, has been released by Microsoft as well as the Visual Studio 2005 extensions for .NET 3.0 and the .NET 3.0 SDK. The downloads are available for Windows XP, Windows Server 2003 and Windows Vista where applicable. The .NET 3.0 is .NET 2.0 extended with new technologies such as Windows Presentation Foundation, Windows Communication Foundation, Windows Workflow Foundation and Windows CardSpace.

When developing applications and/or integrations for Visual Studio 2005 with the Visual Studio 2005 SDK, for example using the DSL Tools, the testing and debugging is done using a Visual Studio Instance that are running with a special registry hive, instead of the normal so you don’t mess up your normal Visual Studio operations. After a while, when you have created a lot of testing applications the Visual Studio interface is bloated with messed up toolbars, menus and templates you will need clear this experimental hive.

The first CTP of the Visual Studio 2005 SDK 4.0 is released to Visual Studio Industry Partners. The release contains Sandcastle, updated setup and improved Vista/UAC support. Note: the download is only available to the VSIP members.

Windows Vista will be released later this year to partners and volume license customers and in the beginning of 2007 to the masses. A successful release of a software product such as Windows Vista requires that a lot of consultants use it and can recommend it to the companies. The last few days it has come out in the open that Windows Vista will not support Microsoft Visual Studio 2005 until the first service pack is released, during the first half of 2007, and even then it will be compatibility issues.

I’m so happy, the DSL Tools V1 is shipped as a part of the Microsoft Visual Studio 2005 SDK V3. I’ve been waiting for such a long time, now we can finish up our designers and make them available to our developers, partners and clients so they will be able to develop more easily. I’m currently downloading it, so I’ll have to see how much has changed since the last beta version, hopefully not that much.

Stuart Kent announces that the documentation for the DSL Tools version 1 are available at MSDN. We’re getting closer to a final release of the DSL Tools. I can’t wait to get my hands on it!

There seems to be some kind of software release frenzy at Redmond right now. Microsoft are spitting out application after application and I don’t mean the two huge ones; MIcrosoft Windows Vista and Microsoft Office (Server) System. Applications, small and big, like Internet Explorer 7, Windows Live Writer, XNA Game Studios, different Microsoft Live applications, Windows Desktop Search and now XML Notepad 2006 are dropping out from the software factory. It’s fun, but it takes me so much time reading and catching up on the releases.

Finally! According to Stuart Kent, program manager at Microsoft, the DSL Tools V1 will be a part of the Visual Studio 2005 SDK Version 3 at the first part of september. I have now a long time waited for this release so we can build our own designers for Visual Studio 2005. Currently my company have a huge demand from our customers that our application should be more easily customized, and the DSL tools will really help us out.

I spend a lot of time using mainly two applications; Microsoft Visual Studio (2003 and 2005) and Microsoft Office (2007). Microsoft Office 2007 introduces a new user interface that simplifies the usage a lot. I am a devoted reader to Jensen Harris Office User Interface blog and it has taught me a lot and given me influences on how user interfaces should be built and I try to take his advices in account.

Microsoft has release Service Pack 1 for Microsoft Visual Studio.NET 2003. The Service Pack contains a number of hotfixes as well as some improvements, read the release notes for more information. I successfully installed the Service Pack, which is not the case for everyone.

For me this second quarter of 2006 has been so interesting with all these beta and CTP products from Microsoft. The summer will be a long wait for the Release Candidates and the autumn a huge and shaky wait for the gold products. Here is a short summary of what i think so far; **Microsoft Expression Graphics Designer**An interesting product which I have big hopes for, I really like, and have just adjusted, to the vector way of doing my graphics.

Yippie, finally a new CTP of the Visual Studio 2005 SDK is available. I’m really looking forward to the upgraded DSL Tools. New features of the DSL Tools include: new file format (.dsl), instead of the old .dsldd and .dsldmd. Now things should be easier to get a grip of and there are more designer support new DSL Designer and more…

Roland Weigelt has updated the GhostDoc 1.9.3 for Visual Studio 2005. Check it out!

I have moved this blog to my own domain, http://www.wictorwilen.se/ and I decided to have it hosted at DotNetPark. DotNetPark has an excellent service at great prices. For me it was important to have ASP.NET and Microsoft SQL Server where I hosted my site and they have all that and more. I can easily publish the site using FTP from Visual Studio and connect to the SQL Server using the Enterprise Manager or Visual Studio.

Scott Guthrie announced that the VS 2005 Web Application Project V1.0 Released . Great! I’ve been waitning for this one, the VS 2003 way of working with web projects worked really nice - and now we can use it with VS 2005!Thanks!!!

I have for a few interesting weeks been using Microsoft Windows Installer Xml, aka WIX, to create an MSI installer for our software solution (finally the number of installation has increased so it was worth it :-).Our software is higly configurable and modularized so I needed to use a tool more advanced that the built-in installers in Visual Studio.Net - and the choice was to use WIX. For you out there who doesn’t know what WIX is then the short story is that; WIX is toolset that builds Windows installation packages from XML source code.

Today, after installing the RTM version of VS.NET 2005, I got some errors due to previous installs of the Betas. One of the was a Package Load Failure for the Class Designer. After a quick search on MSDN Product Feedback Center I found a case (FDBK39168, now closed) with a really nice tool that scans and fixes a number of known issues in Visual Studio.NET. You can download it here: http://astebner.