What is Code Metrics Viewer? – Matthias Friedrich highlights his Visual Studio 2010 Code Metrics Viewer extension which plugs into VS 2010 Professional and uses the Code Metrics Power Tool to provide code metrics information to the IDE. Matthias is blogging a number of posts on this project blog which look at the various features of the viewer and I encourage you to check those other posts out too.
The official Microsoft Kinect SDK beta is now out and available for download! Covered by Channel Nine Live Media, Microsoft Scientist Anoop Gupta made the announcement himself that after the long wait, users may now go to the official SDK website to download the latest software development kit for the Kinect camera.
Here are the features that will come with the Kinect SDK (taken from Microsoft SDK website):
“The Kinect for Windows SDK beta is a programming toolkit for application developers. It enables the academic and enthusiast communities easy access to the capabilities offered by the Microsoft Kinect device connected to computers running the Windows 7 operating system.
The Kinect for Windows SDK beta includes drivers, rich APIs for raw sensor streams and human motion tracking, installation documents, and resource materials. It provides Kinect capabilities to developers who build applications with C++, C#, or Visual Basic by using Microsoft Visual Studio 2010.
Raw sensor streams
Access to raw data streams from the depth sensor, color camera sensor, and four-element microphone array enables developers to build upon the low-level streams that are generated by the Kinect sensor.
Skeletal tracking
The capability to track the skeleton image of one or two people moving within the Kinect field of view make it easy to create gesture-driven applications.
Advanced audio capabilities
Audio processing capabilities include sophisticated acoustic noise suppression and echo cancellation, beam formation to identify the current sound source, and integration with the Windows speech recognition API.
Sample code and documentation
The SDK includes more than 100 pages of technical documentation. In addition to built-in help files, the documentation includes detailed walkthroughs for most samples provided with the SDK.
Easy installation
The SDK installs quickly, requires no complex configuration, and the complete installer size is less than 100 MB. Developers can get up and running in just a few minutes with a standard standalone Kinect sensor unit (widely available at retail outlets).
This SDK is designed for non-commercial purposes only; a commercial version is expected to be available at a later date.”
Additional details about the SDK is that it is currently in beta, meaning it is not yet the actual finished product. Rather, Microsoft wants the opinion of the Kinect hackers/developers in finalizing the product. By keeping it in beta, Microsoft will then ask users to give their feedback concerning the SDK with the eventual hope of releaseing a Kinect SDK built for and with Kinect hackers.
There is also a commercial version coming out. Details are not yet final as to what the difference would be between the two versions of the Kinect.
Source: kinecthacks.com
Yay!! Microsoft has released a Web Standards Update for Visual Studio 2010 that adds full support for HTML5, CSS3 and new Javascript features like Geolocation and local storage. Scott Hanselman has a good write-up on this update in this blog post. There you can see some more detail about what exactly it brings to the VS.NET IDE, etc. Or, if you want to skip all that and go right to the download, you can get it here. At this point in time the HTML5 standard is still evolving. Taking that into consideration, Microsoft plans to provide additional updates every quarter or so to keep up with new features, changes to the draft, etc.
By the way, if you still aren’t familiar with all of the cool things that HTML5 brings to the table you should definitely check out this free online book, Dive Into HTML5, by Mark Pilgrim.
Visual Studio 2008 is not without its faults. They did however add some nice features in the 2008 release such as JavaScript debugging. This feature is great when you need it, but can drastically slow down your debugging experience if you don’t need it or use quite a few “script heavy” controls like Telerik Radcontrols.
So after dealing with this for a while and taking enough productivity hits I decided to find a way to disable the Script Documents folder that shows up when running in debug mode.
It didn’t take long to stumble across this blog post where the blogger made a VisualStudio add-in to make turning this on and off as needed easy via a toolbar button. After reading the post and downloading the utility I was debugging without the old lag that I had before caused by all of the JavaScript documents that were loaded.
If you’ve run into this and feel this would be helpful, I can say that it seems to be working fine for me. I was a little worried too considering I run Windows 7 but it seems to still work well without any permissions issues.
I have been going back and forth banging my head against a wall trying to fix a JavaScript error that was happening on my Reporting Services ReportViewer control when the View Report button is clicked. The error was a JavaScript error and seemed to be related to using something AJAX related on the same page as the ReportViewer control, but it took me a while to figure out what it was and fix it. All of the problems I saw on the web related to using either an AJAX update panel or one of the extenders in the AJAX Control Toolkit. Unfortunately for me I wasn’t using either one of them so trying to figure this one out was tricky.
The specific JavaScript error was:
Microsoft JScript runtime error: ‘this._postBackSettings.async’ is null or not an object
My page was setup where I had a master page with an AJAX menu on it (Radmenu to be specific). In order to use the Radmenu you need a ScriptManager object. Other than the menu, I didn’t have any AJAX related controls on either the master page or the content page.
What I eventually figured out was that my report pages (which use a base class) needed to disable partial rendering. To do this, you must do it in your page’s init event. If you do it after the init you’ll get an invalid operation exception. Here’s the code in the base class (you can put this in your code behind if you’re not using a base class):
Private Sub Page_Init1(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Init ' Make sure this page has a master page If Not IsNothing(Me.Master) Then Dim masterScriptManager As ScriptManager masterScriptManager = CType(Master.FindControl("MasterScriptManager"), ScriptManager) ' Make sure our master page has the script manager we're looking for If Not IsNothing(masterScriptManager) Then ' Turn off partial page postbacks for this page masterScriptManager.EnablePartialRendering = False End If End If End Sub |
Just in case others stumble across this and are trying to solve their problem, here are some of the links I landed on when trying to solve the problem:
Happy New Year!
While this tip isn’t my own, it still seems as though it will be very helpful. I know that I do a lot of development locally where I don’t have an SMTP server setup. This tip, courtsey of .NET Tip of the Day, really will eliminate that problem and allow you to work with email without the headaches.
—
Testing code that sends email has always been a pain. You had to set up a SMTP service just to test that your .NET application sends the e-mail correctly.
However, there is a way to send e-mails with no SMTP server set up. Just configure your .NET application to drop e-mails into a specified folder instead of sending them via SMTP server:
<system.net>
<mailSettings>
<smtp deliveryMethod=”SpecifiedPickupDirectory”>
<specifiedPickupDirectory pickupDirectoryLocation=”c:\Test\” />
</smtp>
</mailSettings>
</system.net>
This will instruct SmtpClient class to generate mail message, save it as .eml file and drop it into c:\Test\ folder.
A co-worker of mine shared this with me recently. It was one of the biggest annoyances in Visual Studio 2005 if you ask me!
How to enable IntelliSense in .skin files
IntelliSence everywhere! That’s one of the biggest features in new Visual Studio .NET 2005 (VS 2005). But guess what, it doesn’t work out of the box in .skin file – the place you really need it. Those of you who worked with ASP.NET 2.0 themes understand me . Good news – there is a workaround to enable this feature. Do the following:
1. Go to Tools->Options menu.
2. Pick Text Editor -> File Extesion fom a tree at the left part of Options dialog.
3. Type skin in Extesion text box.
4. Select User Control Editor from Editor dropdown.
5. Click Add and then Ok to close dialog and re-open your skin files.
6. Say something corny about Microsoft.
Enjoy!
© 2013 Don Kitchen · Proudly powered by WordPress & Green Park 2 by Cordobo.
Valid XHTML 1.0 Transitional | Valid CSS 3
