So I had a really annoying thing happen today with Word 2007. I was trying to work with a document and it would not let me select the text using my mouse.  Hmmmm... thats weird??  So of course I do what any sane person would do... Reboot ;)

Well that didnt fix it (I thought maybe it was a result of docking/undocking without a restart)

After digging around a bit (Googling) I found out I was not the only one to have this problem. I am still not sure what caused it but was able to find a fix.

****  Use at your own risk *******

. Close Word and Outlook
2. Start / Run and type regedit
3. Navigate to HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Word\Data
4. Rename this key.
5. Restart Word

That fixed the problem for me. Maybe when I have time, I will hunt down the actual reason for this but for now I need to use word ;)

Doc

Here are the files for my Building an ASP.NET Website from End to End Talk Today.

Download Files

Doc

Working with SQL output Caching and SQL 2005 is a little different then working with SQL 2000. Here is a great resource on how to set this up for your ASP.NET pages.

http://msdn2.microsoft.com/en-us/library/ms379559(VS.80).aspx#caching_topic2

I could not have said it better myself ;)

Doc

Just in case anyone else is having problems getting debugging to work with Visual Studio 2005 and IIS7, here is a link that will fix your problem.

http://mvolo.com/blogs/serverside/archive/2006/12/28/Fix-problems-with-Visual-Studio-F5-debugging-of-ASP.NET-applications-on-IIS7-Vista.aspx

Thanks Mike….

Hey…. I made it into the Seattle PI newspaper. Pretty cool ;)

I was actually posting the Bill post below.

Pretty cool

Doc

Security in today's world is evolving at a rapid pace. In the early days(86 -95) the threat was localized to individual workstations or individual LANS.

When the internet took over, things just exploded. Peer to Peer, Social Engineering, root kits, have been proliferated by the ease at which a hacker can transfer his/her virus/worm. This session talked about what has been, and what MS had in mind for the future. I will blog more about this later. He talked a lot about SDL (The security Development Lifecycle) . If you are interested, there is a great book on the subject.

Check it out on Amazon etc…

Happy programming

Doc

So I am at the keynote for the MVP Summit and Bill (Yea, we are on a first name basis) just finished his "speech". We are now in the Q&A phase. It has been quite interesting. There have been some great questions on where Microsoft is going in the future, what he thinks is going to really take off but has not yet (tablet, voice recognition) .

One of the best questions was from someone who had started on the Alistair. He read the back panel that instructed users that needed help to Call Bill or Steve… What a crack-up. He got Bill to sign it for him ;)

Well off to another session… more soon.

Doc

I received a question for a blog reader the other day complaining that they could not find the <machineKey> element in their Machine level web.config or their machine.config file. It was quite puzzling to them and thought that someone may have removed it.

Well, they were right and wrong. Someone did remove it, but that someone was Microsoft.

When .Net 2.0 came out, they did some "reconfiguring" of the config files. The first thing you will notice is that they moved most of the items that developers may want to change to a "Machine-Level" web.config file which can be found right alongside the machine.config file in the C:\WINDOWS\Microsoft.NET\Framework\v2.x\CONFIG folder. The second thing they did was remove elements from the machine.config file that were set at their default level. So if you don't want to change the machineKey, it will be set like the following.

You can find these settings in the web.config.comments file in the same directory.

You can of course override the defaults by adding the element to the machine.config, machine-level web.config, or a web.config in your application.

Happy programming

Doc