The SharePoint Developer Team just blogged to clear any confusion around the future of Sandboxed Solutions:
Read more here …
Do you remember the SPDisposeCheck Static Analysis RuleSet for Visual Studio 2008/10 ? It was pretty nifty, I’ve used it in many SharePoint 2010 projects and it did a great job. Yesterday, I decided to upgrade it to work with Visual Studio 2012 and I’ve published it today on CodePlex. You can get it from here.
This wonderful RulSset has been originally created by Stephen Vick, I just tweaked it a little bit to make it work with Visual Studio 2012.
What is Visual Studio Static Code Analysis ? http://msdn.microsoft.com/en-us/library/3z0aeatx.aspx
What is SPDisposeCheck ? http://archive.msdn.microsoft.com/SPDisposeCheck
By using SPDisposeCheck from within your Code Analysis, you can avoid any future memory leaks that might occur because your developers didn’t properly dispose the SharePoint API objects. You can even prevent bad code from entering your Source Control system by creating a check-in policy that performs Static Code Analysis and spot any issues earlier.
I have created a video that explains the setup steps and shows you a quick example. You can watch it here.
In the previous two videos, I’ve showed you how to do Test Automation for SharePoint using Coded UI Tests in Visual Studio 2012 Premium or Ultimate. I’ve also showed you how to run your coded UI test multiple times with different sets of data to test different conditions “Data-driven Coded UI Tests”.
Today, I’ll tackle another area which is Manual testing. In today’s video, you will learn how to use Microsoft Test Manager 2012 to author a manual test case for your SharePoint Application and take advantage of test parameters. I will then run this test case using the Microsoft Test Runner against my SharePoint Application. While running this test case I will capture an action recording which can be used to take advantage of Fast Forward for Manual Testing, to quickly re-run test steps or even entire test cases in the future “Fast Forward for Manual Tests”. You can watch the video here.
Please note that you might need to change the quality to 720p (HD) as shown below for the best experience :
You can use Visual Studio 2012 to create automated tests of the user interface (UI) known as coded UI tests. These tests provide functional testing of the user interface and validation of user interface controls. Automated UI tests enable you to test that the user interface is functioning correctly after code changes. They are quicker to run than manual tests. Therefore, you can run them more frequently.
Visual Studio 2010 partially supported Coded UI Testing for SharePoint while Visual Studio 2012 was pretty close to fully supporting this but there were a few SharePoint specific issues that the product team wasn’t able to address that made CodedUI (functional testing) not work well for SharePoint. In Visual Studio 2012 Update 1, those issues were addressed and now Coded UI Testing is fully supported for SharePoint 2010.
I’ve recorded a quick video (in Arabic) to help you quickly get started with Coded UI Testing for SharePoint, you can watch the video here
Please note that you might need to change the quality to 720 px (HD) as shown below for the best experience :
I was super excited on Sep 12th when I first read Brian Harry’s announcement about the enhancements done in the Web & Load Testing tools in Visual Studio 2012 Update 1 to completely support SharePoint. Here us a snapshot from the first announcement :
Yesterday, I was trying the tools for the first time & created a video in Arabic to show the new features and tool enhancements, you can watch the video here http://youtu.be/VVhRTikOnI4
Appreciate your feedback as usual
After I published the “SharePoint & IntelliTrace” video the other day, I received many requests for another video about the “SharePoint Emulators”. I fired up Camtasia and recorded a quick video to get you guys introduced to this new feature. You can watch the video here.
– ShimNotSupportedException when trying Visual Studio 2012 SharePoint Emulators
– [Arabic Video] Visual Studio 2012 IntelliTrace Support for SharePoint
With IntelliTrace in Visual Studio Ultimate 2012 Update 1, SharePoint developers now have a way for directly using Correlation IDs to diagnose production issues originating from SharePoint custom code as well as debugging & fixing it.
Traditional debuggers give SharePoint developers only a snapshot of the state of their applications at the current moment. However, IntelliTrace can be used by SharePoint Developers to review, and even navigate to, past events that occurred in their applications and the context in which the events occurred. This is also known as “Historical Debugging”
I’ve created a quick video in Arabic to walk you through a real-life scenario in which IntelliTrace was used to quickly diagnose and fix a production issue. You can watch the video here ..
For the English version of the video, you can watch the one available on Channel 9.