If you are on Win 7 (any build) you will find quickly that Daemon tools don’t work on that. Even if it was working, I would in any case recommend ditching Daemon tools and recommend using Virtual Clone Drive which not only is free but also works like a champ. I use it on Vista as well.
Oct 24 2008
PDC’ing
I am going to be at PDC – anyone else I know going to be there? If you are reading this, and are going to be there then it is quite likely you know how to ping me and let me know you going. It also might be a good idea to check out the Devil’s field guide to the PDC.
I will be blogging from there – but not during the sessions – need to ensure I am not distracted – especially as the Avalanche is coming! Expect to get some posts later in the evenings.
Oct 14 2008
Win 7 called Win 7
Not since the days of NT 4.0 (which stood for New Technology btw) has this happened that Microsoft is calling a Windows version what is really is – so Windows 7 will be called Windows 7! I say Yay! It is about time the stop all the malarkey about funky code names and boring “release names”.
Mar 28 2006
Sharepoint v3 Installation Fails
I was trying to setup Sharepoint “v3″ which is part of Office 2007; the Beta 1 Technical Refresh installs without a problem, but when I try and configure Sharepoint it fails in Step 2 and I get the error shown below. You can click on the image to see the full size.
However, when I trawl through the log file, I did find a few exceptions, a couple of which are listed below. The only reason the font is small on those is so it would fit and render fine in here. You can copy and paste that in notepad or something and see if in a bigger font; alternatively you can download the log file (see the end of this posting).
Exception 1:
Entering function CreateCentralAdministrationSiteForm.CreateCentralAdministrationSiteFormInitializeBeforeShow
…
A SocketException was thrown with SocketError ConnectionRefused
Connect has been refused for port 12838, so we will consider this a free port
Have not found a free port yet. Number of tries is 1. Min port we will try is 1024, Max port we will try is 49151
Leaving function CentralAdministrationSiteTask.GenerateRandomUnUsedPortForTheAdminVs
Leaving function CreateCentralAdministrationSiteForm.CreateCentralAdministrationSiteFormInitializeBeforeShow
Exception 2:
Entering function ResourceAccess.SetAccessRule
Entering function ResourceAccess.SetRegistryAccessRule
Entering function ResourceAccess.RetrieveRegistryRightsFromResourceAccessPermissions
Leaving function ResourceAccess.RetrieveRegistryRightsFromResourceAccessPermissions
Task secureresources has failed with an unknown exception
Exception: System.InvalidOperationException: This access control list is not in canonical form and therefore cannot be modified.
at System.Security.AccessControl.CommonAcl.RemoveQualifiedAces(SecurityIdentifier sid, AceQualifier qualifier, Int32 accessMask, AceFlags flags, Boolean saclSemantics, ObjectAceFlags objectFlags, Guid objectType, Guid inheritedObjectType)
at System.Security.AccessControl.DiscretionaryAcl.RemoveAccess(AccessControlType accessType, SecurityIdentifier sid, Int32 accessMask, InheritanceFlags inheritanceFlags, PropagationFlags propagationFlags)
at System.Security.AccessControl.CommonObjectSecurity.ModifyAccess(AccessControlModification modification, AccessRule rule, Boolean& modified)
at System.Security.AccessControl.CommonObjectSecurity.ResetAccessRule(AccessRule rule)
at System.Security.AccessControl.RegistrySecurity.ResetAccessRule(RegistryAccessRule rule)
at Microsoft.SharePoint.PostSetupConfiguration.ResourceAccess.SetRegistryAccessRule()
at Microsoft.SharePoint.PostSetupConfiguration.ResourceAccess.Secure()
at Microsoft.SharePoint.PostSetupConfiguration.SecurityTask.SecureResources()
at Microsoft.SharePoint.PostSetupConfiguration.SecurityTask.Run()
at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
I think I have everything outlined in the installation document for the Beta 1 Technical Refresh. BTW, I have this on Windows 2003 Enterprise Edition with SP1 and all latest patches. SQL Server 2005 Dev. Edition and VS.NET 2005 Professional Edition.
There are a couple of more exceptions along the same line – if it would help I have upload the full log file which you can download here (53 kb). But the real question is any idea what is broken and why?
Jan 06 2006
System Stability Chart in Longhorn
If you go to the Computer Management tool in Longhorn (Dec CTP), then you will something called the System Stability Chart, which shows you how stable the system has been including Software Installs/UnInstalls, Failures (including Apps, Drivers, Hardware, Windows), etc. Its pretty cool and should help narrow down cause of failures – quite helpful in a corporate environment. Here is a screen shot from one of my VMs.
Jul 28 2005
Vista Beta 1 now available on MSDN
A colleague of mine, pointed this out and seems like MS has released the Beta 1 for Longhorn (now called Vista), on MSDN. If you are universal subscriber you can download it. But, its a hefty 2.GB d/l! Below is my screen shot from my login.
Jun 09 2005
Update on ClickOnce
Well it seems I stand corrected (sort of), and these are rare moments so enjoy it.. *grin*, seems like it was a user error (again sort of – in a minute on that) when I talked about the issues with ClickOnce earlier. The problem there was that the installation can only be supported via http and not using ftp (which I have chosen), once you change it to http you are golden. Moving on, why do I say a user error (sort of)? Well mainly because the Publish Wizard as far as I can see is not very explicit about this and unless you know (which now you do), you will get into this issue.
So my recommendation is not to use the wizard at all but instead go straight to the options page, which not only has more features but also gives you more control. How do you get there? Thought you would never ask. Right-click on your project name in the Solution Explorer and select properties. In the new window select the second last tab on the left called Publish – voila you are there. If you see the screen shot you will notice I have highlighted the urls you need to be careful of. This is where you can add other external dependencies, called Prerequisites (which were not automatically picked up as they are not referenced at design time). Most of the other options are self explanatory.
Also, if you go over the Sandbox to check out the Clock v2.0 (which was recompiled for Beta 2 – no new features other than to get it compiling), and try to install it, you will notice you cannot; instead you would see a funky looking xml (ain’t that funky btw). Well that is because the “.application” MIME type is not registered on the server that hosts this site. Since this is not a dedicated server, I don’t have any control over it and cannot just “switch it on” – I need to open a ticket for that and not sure how that will go. But, till then if you do look at the xml you can find out some of what is under the skin of ClickOnce.
Apr 27 2005
.NET Framework 2.0 Beta 2 Obsolete APIs
In the Beta 2 version of the .NET Framework 2.0 product, there are various APIs that have been added in since V1.1, but are marked obsolete. All of these APIs will be removed from the product at V2.0 release. These are APIs which were added during the beta cycles of the V2.0 product lifetime, but as a result of design changes and/or product feedback, have subsequently been replaced, or will simply be removed. It is paramount for your ability to easily move forward to the final V2.0 release of the product that these obsolete APIs not be referenced. This list is the APIs which will be removed before the final release of V2.0.
You can download the list from here.
Apr 26 2005
Got a space to play with ASP.NET 2.0
Not sure if you were keeping an eye or not, but I got some space to play with ASP.NET – something that is exposed to the net and not only my machines at home – does bring up some interesting possibilities. If you want me to upload some code that you might have to run then let me know, we just need to coordinate as I cannot create subfolders (unfortunately) – yet anyways. 
Mar 28 2005
What is new in IIS 7?
Though there have been lots of talk in Longhorn (especially recently), and I have dabbed in it previously, now some interesting bits are being released on what are the new features in IIS 7. The coolest one of these is the componentization of IIS where all of IIS’s functions will be specific components which can be turned on or off. This means that when you install the Web server, you’ll be able to add only the functionality you need, one piece at a time.
For example, if your applications do not use CGI, you can simply remove that component from your IIS configuration. Today, IIS functions are mostly monolithic, making you install core functionalities whether you use them or not. When a patch for CGI comes around, you need to apply it even though you don’t use it. With IIS 7.0, you’ll need to worry only about the components you chose to install. This will support even more secure configurations of IIS.
In addition, the componentization of IIS will allow Microsoft to build the service onto a set of public APIs which will allow third-party vendors to build their own functionalities into the Web server. And because each functionality is a specific component that can be added to or removed from IIS, these third-party add-ons will be completely transparent to the system.
Another key aspect of IIS 7.0 will be its complete integration with ASP.NET. Currently, ASP.NET consists of additional functionality that is tacked on top of IIS. Although they integrate well, it still takes two different sets of instructions to manage the two together – IIS is managed through its Metabase, and ASP.NET is managed through web.config files. In version 7.0, IIS will be completely integrated with not only ASP.NET but also the .NET Framework, ADO.NET, and even Indigo – the next version of the Microsoft Web Services platform. This means that there will be a single configuration point for all components of an application and the engines used to run it. The greatest advantage of this level of integration is that you will be able to deliver an application complete with its associated Web server configuration when you need to deploy it. This will vastly simplify administrators’ jobs.
Feb 09 2005
Indigo out in the open
Indigo is now out in the open and you should see a lot of flurry about it soon. This is cool. I have had a chance to look at bits and pieces of it in the past and could not talk much about it due to NDA, but that hopefully can change soon.
[Listening to: Track 03 - New Artist (38) - New Title (38) (05:05)]
Next Page »