Archive for the ‘Microsoft’ Category

Launch of Visual Studio 2010 & Dotfuscator CE 5

Monday, April 26th, 2010 by Brandon Siegel

With the launch of Visual Studio 2010 and Silverlight 4 at the DevConnections show in Las Vegas last week, I am pleased to announce that Dotfuscator CE version 5 is now generally available. With an all-new user interface, more intelligent obfuscation, and application analytics instrumentation, this promises to be the biggest change we’ve made to Dotfuscator CE in its history. I am particularly excited because soon, with the application analytics included in Dotfuscator CE, millions of developers world-wide will have the opportunity to see real usage data coming in from their applications. Even better, they will be able to do so completely cost-free.

I was invited to act as part of PreEmptive’s delegation to the launch event and humbled to speak with so many passionate developers, architects, DBAs, and yes – even managers. What I did not initially expect was the overwhelmingly positive response from nearly everyone we talked with. Most people had never heard of application analytics. But, with a brief introduction everyone quickly understood the idea and many offered up scenarios where they would want to use it for their applications (completely unsolicited, I might add). It was thrilling to receive such a positive response to something I - and the other fantastic developers here at PreEmptive - have worked very hard over the past few years to create.

I very much encourage the great folks I met in Las Vegas last week, along with millions of passionate developers across the globe, to open up Dotfuscator CE and try out the free analytics we’ve included. Today, most web developers wouldn’t think of publishing a web site without including web analytics. I hope that having these analytics included with Visual Studio 2010 will lead to application developers thinking the same way about their applications. Of course, using the two together in a Silverlight or ASP.NET application to get a complete view of the visitor’s experience is a natural fit. But application analytics extends far beyond that. Now, all .NET developers are able to get live information that can help steer development focus, even in areas that were previously completely opaque – from cloud apps running on Windows Azure to mobile phone applications on Windows Phone 7 and even to applications running on Linux and Mac with Mono.

In fact, I look forward to seeing how application analytics will be used to support open source development throughout the .NET ecosystem. Because open source developers essentially donate their spare time, being able to focus their efforts in places that have the most user impact is crucial. An open source development model also allows far greater flexibility for developers to immediately shift their focus to match what their users are actually doing with the software they produce, without the constraints of rigid development and deployment practices. Because of these factors, I specifically encourage maintainers of open source projects to try the free application analytics provided in Dotfuscator CE. Together with the bug reports and feature requests you already have, you will be able to truly make the most of the precious time that your contributors give.

Some might say that it’s counterintuitive for a company known for source code obfuscation to support open source development, but at PreEmptive our guiding principle is simply “help software succeed”. With application analytics, we have the opportunity to extend our dedication to this principle beyond proprietary software. In the past few months, we’ve released numerous projects on CodePlex including some awesome editor extensions that integrate application analytics right into the Visual Studio 2010 IDE, an endpoint starter kit so you can write your own backend to receive and process Runtime Intelligence messages, a data visualizer sample to demonstrate how to consume analytics data using our RESTful analytics API, and an API helper library to make using our API even easier. And our new partnership with CodePlex, which will provide free application analytics for hosted projects surfaced right within each project’s page, provides us yet another great opportunity to help software succeed.

Today is the first day of Microsoft’s MIX10 Conference

Monday, March 15th, 2010 by Gabriel Torok

One of the items being announced today by Microsoft at MIX is the SilverLight Analytics Framework. The Silverlight Analytics Framework will let designers and developers visually build analytics into their Silverlight applications using Microsoft’s Expression Blend.

Now, most readers of my blog already know that Developers can already inject Runtime Intelligence analytics into Silverlight (and any other managed code) using Dotfuscator inside Visual Studio. I am excited about this new framework because it offers an entirely new way to configure runtime intelligence (using Expression Blend) and that means a whole new community of users also have access to analytics for the very first time. This is also being echoed by Michael Scherotter, principal architect evangelist at Microsoft Corp. and architect of the analytics framework. He writes that we have “successfully used the Silverlight Analytics Framework to open its application instrumentation to a new audience of designers.”

Runtime Intelligence offers the following advantages over traditional Web analytics services:

· The analytics endpoint (and the resulting data) can be self-hosted and managed by the application provider (you don’t have to send your data to a third party – but that option is also available too).

· While the resulting Web analytics maps to the Silverlight Analytics Framework data model, the underlying SOAP schema is shared with Dotfuscator’s instrumentation.

The common schema allows Dotfuscator to provide a complimentary instrumentation mechanism for any .NET Framework component. THIS means that

· Middle and back-office application tiers can be instrumented providing a deeper view across distributed application workflows.

· Older or alternative applications using WPF or some other non-Silverlight form factors can be benchmarked against the newer Silverlight applications to track both user behaviors and application usage.

The world of application analytics is about to take a big step forward. In fact I believe that one day in the not too distant future application analytics will be as common as web analytics is today and the distinction will eventually disappear.

What decisions could you make to better serve your customers, to reduce your costs, and improve your products if you had ready access to usage data streamed to you from the wild?

Tell me what you would do - I would love to hear from you.

PreEmptive is doing its part to help the Vancouver Winter Olympics go off smoothly.

Friday, February 19th, 2010 by Gabriel Torok

Online viewers of the Vancouver Olympics on NBCOlympics.com are using Silverlight based video and photo viewers delivering full HD quality content for viewers and helping content owners monetize their content. I am pleased to say that Dotfuscator had a hand in all of this innovation providing both protection and optimization for the high performing video player at the heart the NBC online Olympic experience.

For an overall description of the Silverlight solution, see: http://team.silverlight.net/events/let-the-games-begin/

For Microsoft’s own description of the role of partners (including us of course), see: http://team.silverlight.net/customer-evidence/vancouver-olympics-ndash-how-rsquo-d-we-do-that/

The development teams especially appreciated the fact that Dotfuscator can accept and output XAP files (instead of low level DLLs that force developers to manually edit XAP files).  This shortens and simplifies the release process – and was critical for an event like the Olympics.

On an unrelated Silverlight note, I was pleased to see David Kelly’s recent blog entry . This Silverlight MVP has identified Dotfuscator’s Silverlight analytics as “a critical tool in your tool Silverlight toolbox.” Good Stuff.

How do I love thee? Let me count the ways.

Thursday, August 20th, 2009 by Sebastian Holst

“How do I love thee? Let me count the ways. I love thee to the depth and breadth and height” - Sonnet 43, Elizabeth Barrett Browning

So “what’s love got to do with it?” (Private Dancer, Tina Turner) Hint: if people live for love, then businesses live for money

On July 14th, Microsoft announced Azure pricing and a “grace period” through PDC 2009. A primary rationale here is to enable development organizations to optimize deployment and monetization models to maximize Azure commercial opportunities.

So, whether you are a romantic (like Ms Browning above) or perhaps more hardened like Tina Turner’s Private Dancer (or Stanley Kubrick a la Full Metal Jacket), one thing is for sure - Microsoft wants Azure to “love you long time.” How deep, wide, high or long is the question.

Check out a this article in SD Times - PreEmptive’s Dotfuscator instruments Azure applications By David Worthington – where Dave Worthington makes many of the very same points.

Of course, we announced Runtime Intelligence Service (RIS) Azure support to help developers answer these very questions. While perhaps not as soaring as a sonnet – Runtime Intelligence allows for any .NET component deployed into Azure to be injected (post-build) with session, feature and method level monitoring. The runtime intelligence is streamed out of Azure for analysis. Other than writing a custom solution, this is perhaps the only means to measure adoption, usage patterns and performance inside Azure in near real-time.

Now, my posts are all intended to help you (blog followers) find more ways to make more money (we want to spread the love). So, you will note that I very specifically said the RIS helps to answer these questions. What the Azure development community really needs is an ROI calculator that will combine real usage data (from both legacy and piloted Azure applications) with Microsoft pricing and the offset IT expenses to come up with an Azure ROI calculator. I know there are lots of calculators being written – but how many of them can incorporate actual usage data before and after deployment to the cloud? That’s not our business – but could it be yours?

If yes, let me know and I will make sure you have what you need to call our RI Service via our RESTful API – making your calculator uniquely able to reliably predict cloud ROI.

As always, i have a more philosophical take on this issue on my personal blog at http://apps-are-people-too.blogspot.com/2009/08/how-do-i-love-thee-let-me-count-ways.html

How to sell to over one million .NET developers with VS 2010 and VSTS 2010

Monday, June 15th, 2009 by Sebastian Holst

Roughly 15% of all Visual Studio developers have used Dotfuscator Community Edition (CE) to prevent reverse engineering (and I think we can all agree that this is a relatively specialized requirement). If you accept the next uncontroversial assumption that more developers would want to know who is using their software, how and why than would be concerned about reverse engineering – then we can also assume that the new Dotfuscator CE that includes application monitoring capabilities will be adopted by perhaps 2X or even 3X more developers – or between 30% to 45% if the 6 million+ Visual Studio users.

This next series of posts will outline specific opportunities for entrepreneurial developers to build solutions targeting the millions of .NET developers likely be using these new capabilities as VS2010 reaches general availability.  For an earlier example of this, see my blog entry how to make $5 from every .NET developer on the planet.

Post 1 – Code coverage!? I got your code coverage right here pal!

If you think development teams would benefit from being able to readily reconcile testing code coverage results with beta usage code coverage to improve quality and reduce development costs – read on…

With VS2010 Dotfuscator CE feature tracking, you can stream back feature usage during a beta release that can provide a complete picture of what methods were called, in what order and on what technology stack. If only there were an easy way to not only visualize this in the context of the application’s code base but also to overlay this information on earlier testing code coverage results to ensure I have tested what is being used and my beta users are using what I think needs to be tested! That might be an opportunity…

We’ve got an “opp” for that! (apologies to the iPhone ad guys). If you have evaluated VS Beta 1, you may have already noticed that VSTS 2010 Architecture is a completely new release which leaves behind the current Distributed System Designer and the underlying System Definition Model (SDM ) and replaces them with the Unified Modeling Language (UML), Domain Specific Languages (DSLs) and other tools that are not related to UML. The specific tool I want to point to here is the Architecture Explorer (AE).  AE visualizes relationships inside code using the Directed Graph Markup Language (DGML). By extending the DGML, one can use the Architecture Explorer to create visual models of assemblies – post-build – combining both the relationships inside the code (this comes with AE out of the box) and testing and usage coverage results by extending the styles already included in AE. In short, The Architect Explorer with its DGML support and the ability to extend/modify styles offers an ideal means to quickly reconcile usage data with testing code coverage (and platform and framework coverage as well).

This screen shot shows a generic rendering inside the VSTS Architecture Explorer. The rendering is entirely driven through XML data and, as such, can be easily extended to provide specialized views that are relevant across the entire lifecycle of an application.

In this case, the color schemes (or fonts or sizes) can be driven by:

The level of testing completed as reflected inside a TFS repository to quickly answer the questions

  • Testing status – how much testing has been completed?
  • Testing the right things – are there components that should be getting more (or less) attention?

The level of usage by beta test users as reported via the instrumentation capabilities included in Visual Studio 2010 Dotfuscator CE to quickly answer the questions

  • Beta adoption sufficient – have enough users actually run the software through its paces?
  • Critical path coverage – are the new components being exercised as expected?
  • Testing coverage map to usage profile – combining both testing data and usage coverage data can identify areas of code that are not being tested sufficiently given the patterns of usage that are being observed? (mash up)
  • Platform/framework coverage – are enough users evaluating on Vista SP1 or .NET 1.1 or …?
  • What exceptions have been detected that have not been reported through other channels?