Windows Vista SP1 etiketine sahip kayıtlar gösteriliyor. Tüm kayıtları göster
Windows Vista SP1 etiketine sahip kayıtlar gösteriliyor. Tüm kayıtları göster

Çarşamba, Ocak 21, 2009

Visual Studio 2010 CTP VPC: Dealing with Activation Messages

Conjunction with PDC 2008, we are releasing the first Community Technology Preview of Visual Studio 2010 and the .NET Framework 4.0. You can download the release here (also see my download manager post here for a better download experience). This is an exciting release, and is jammed packed with a ton of great new features. One really nice thing about this release is the amount of work that the product teams put into writing walkthroughs which will guide you through most of the new features. I believe this will be our highest-quality Community Technology Preview yet, and we're excited to start getting your feedback on it.

This CTP is being delivered as a Virtual PC (VPC) image that you can download and run locally. In the future, we will provide a way for you to install the software on your own machine, but given where we're at with building the product the setup experience isn't quite ready. The VPC image gives us a great alternative for getting the software to you as early as possible.

This blog post is about the Activation messages you will encounter with this VPC image. In most cases, you can just ignore these messages and continue using the image. These messages are due to the way in which Windows Server 2008 and Office 2007 evaluation software works. For obvious reasons, our release criteria for distributing VPC images requires that we only ship trial software instead of fully licensed software. In the past, Windows evaluations could be configured to expire on a precise date. Due to changes in Windows Server 2008, we no longer have a firm expiration date, but there are Activation reminder messages which will appear while you are running the VPC. The good news is that these Activation messages will not cause Windows to stop working; however, you will have to dismiss some Activation messages from time to time. Note that Word/Excel/Project and Visual Studio may eventually stop working as explained below, but I have provided workarounds in all instances.

Activation Toast
While running this VPC image you will encounter a "toast" from time to time asking you to activate Windows.
Workaround: You can simply ignore this toast, or click the "X" to dismiss it.


"Activate Windows Now"
Starting sometime in November 2008, you will receive a modal dialog every time you boot this VPC image.
Workaround: To continue, simply click on "Activate Later." You will have to wait a few seconds before this option becomes available.

Word/Excel Activation
The trial versions of Word and Excel which are installed in this VPC image will only work 20 times. Every time you launch Word or Excel you will be reminded of this. After 20 uses, most Word and Excel functionality will stop working. You can still read Word and Excel documents, but you will be unable to use any of the Ribbon functionality. This means that some of the walkthroughs dealing with Word or Excel will not work.
Workaround: The first 20 times you launch Word or Excel, you can simply click "Cancel" to dismiss the activation dialog. After that, if you wish to continue using Word or Excel you will need to revert to a fresh copy of this VPC image. You can download the original VPC here.
After 20 uses, the Ribbon functionality in Word and Excel will become greyed out:

Project Activation
The Microsoft Project trial installed in this VPC image utilizes a similar limited-use mechanism to that of Word and Excel. Project will work 25 times. After that, you can no longer use Project in this VPC image. It is recommended that you only launch Project if you intend to use one of the walkthroughs that require it.
Workaround: If you need to use Project more than 25 times you should revert to a fresh copy of this VPC image. You can download the original VPC here.

Visual Studio 2010 CTP Expiration
Finally, the Visual Studio 2010 CTP will eventually expire. After January 1, 2009, you will no longer be able to launch the Visual Studio 2010 CTP. This is due to a hard-coded expiration date in this CTP. CTP's are pre-release software, so they aren't designed to run forever.
Workaround: If you need to continue using this VPC image after January 1, 2009, you will need to roll back the system clock in your VPC to an earlier date. In order to do so, please follow the instructions post here. Note that you should not roll back your system clock to a date prior to your last interaction with Team Foundation Server, because otherwise Team Foundation Server will get confused. If possible, I would suggest rolling back to a clean copy of the VPC (uncompress the original) and immediately disabling your clock prior to launching it for the first time.

Additional Notes
- No Internet Connection: This VPC image ships with Internet connections disabled. It may be tempting to want to enable an Internet connection on this VPC image in order to supply your own product key and activate this image. However, due to security reasons we strongly advise you not to connect this VPC image to any networks (intranet, Internet, etc.). There are also naming conflicts which can occur if you have multiple VPC images on the same network. Changing the computer name of this machine is not a suitable workaround, since it will break many of the walkthroughs and services.
- Hyper-V: This image was designed to work with Virtual PC 2007 SP1. We have had reports from people who have successfully converted this image to work with Hyper-V (see Grant Holliday's blog), but this may result in additional Activation implications which differ from the scenarios documented above.

In Summary
These Activation messages might seem a bit "broken" at first, but by following the workarounds explained above we hope you'll have a great experience with this VPC image. We are excited to show you a preview of what we're building, and we welcome your feedback! To provide us with your feedback, or get additional assistance using this VPC, please visit

Source: Brain Dane

Cumartesi, Nisan 26, 2008

What does Windows Vista SP1 Mean for Developers?

Aside from the inevitable bug fixes and enhancements to support new hardware types, one of the underlying changes is that SP1 brings the Windows Vista and Windows Server 2008 codebases together.WV-SP1_h_rgb_3

This is a big deal, but it's surprising how few people have noted it: this is the first time we've ever had a common codebase for Windows that goes all the way from a budget consumer PC right up to a mainframe-class datacenter server. Internally to Microsoft, this makes it easier for us to provide sustained engineering on the product: if we want or need to update a system component, we only have to produce two binaries (x86 and x64) for all languages and product editions. Compare that to the days of Windows XP/2003, when we had maybe 25 different language editions and x86 and x64 variants for both client and server OS releases, and you can see how the testing matrix has become a lot simpler! Externally, the benefit is of course that simply by updating to SP1, you get the benefit of a kernel that has been through an extensive server-hardening process. (Check out this Channel 9 video I recorded last year with Eric Hanson to get just a small flavor of the stress testing work that we do with every build.)

Beyond the kernel and subsystem improvements, Windows Vista SP1 brings major improvements to IIS 7. Comparing the original Windows Vista "RTM" version against that shipped with SP1 is like comparing the basic and premium models of a car - the SP1 version of IIS contains all the features added to create the server-strength edition (with the caveat that Windows Vista SP1 is obviously not licensed for use as a commercial-scale production Internet web server). As a crude measure, compare the two screenshots of the administration console below - the left image is of Windows Vista RTM, the right is of SP1:


You'll see other changes to Windows Vista that affect certain relatively niche groups of developers. Direct3D receives a minor update to 10.1; there are new APIs to control the Data Execution Protection and Kernel Patch Protection features; and there are new cryptographic and random number generation algorithms available for developer use. As ever, more information about these features can be found in the Windows SDK.


As a .NET developer, you'll notice that Vista SP1 updates the installed .NET components to .NET Framework 3.0 Service Pack 1. The good news is that many of the enhancements from .NET Framework 3.5 are included in 3.0 SP1 - for example, everything apart from System.AddIn and the Firefox XBAP support is included in Windows Vista SP1. This is a little bit confusing, but it probably helps to know that each of the last .NET Framework releases have built on top of each other, rather than existing side-by-side. The diagram to the right demonstrates this.

As a result, all the CLR and class library enhancements that were made to existing assemblies in 3.5 are incorporated in 3.0 SP1 (mscorlib.dll is updated from 2.0.50727.312 to 2.0.50727.1434); the binaries are identical to those shipped with .NET Framework 3.5. The only difference between 3.0 SP1 and 3.5 is that 3.0 SP1 doesn't have any of the new assemblies ("green bits") added in 3.5 for new capabilities like LINQ. Of course, if you've already installed .NET Framework 3.5 on your Windows Vista machine prior to installing SP1, you'll still have the full 3.5 release on your machine afterwards.

The many other nice features in SP1 for end-users and IT Professionals are outside of the scope of this entry, but suffice it to say that some of the major peeves have been addressed: UAC is less aggressive, file copy performance has been greatly improved (and it takes less time to "estimate"!), application compatibility is better, resuming from standby is faster, and over a thousand bugs have been fixed. For more detail on all these items, check out the main Windows Vista Service Pack 1 site.

It's worth noting in closing that many of the above fixes at least have been delivered via Windows Update over the last twelve months. We're moving away from the old-school approach where service packs were the main way that fixes were delivered to a more agile model where patches are available via Windows Update (or its enterprise equivalent, WSUS) and then rolled into a service update at a later stage. The goal is to reduce the gap between us fixing something and you seeing the results of that fix.

Well, what are you waiting for? Go install Windows Vista Service Pack 1!

Thanks, Tim Sneath...