# Tuesday, March 27, 2007
In the infancy of my career as a beginner programmer, I learned from the very beginning that planning and design is usually 60% of our work, and following through with implementation is 40% of what we do. Deploying a server is no different from deciding exactly on the topology of the server, to the thumb twidling of waiting for the status bar to reach 100%. In the end, a machine that started out as a workstation will never be a server, and reciprocally a sever will never be a workstation. My reality consumed a good two months in the wrong direction, and my hope is will help as a warning from my experience.
Tuesday, March 27, 2007 5:08:10 PM UTC  #    Comments [0]Trackback
# Monday, December 4, 2006

All Internet Explorer users —> NOW HERE THIS! <—

There two more gotch’yas I’ve recently stumbled across that I hope to save everyone that same trouble from:

1)      If your friend has provided you a login to his website running IIS and without 128-bit SSL, HTTPS encryption, make sure you disable “Enable Windows Integrated Security,” or you’ll be forever disallowed to login to your friend’s site.

2)      Don’t ever expect to use Internet Explorer for access to your favorite FTP sites anymore. For security concerns, FTP access is turned off in Internet Explorer 7.0. You are now restricted to use FTP access only through an Explorer Window to keep your files and password from being sent in clear text across the wire.

I hope this helps for everyone that is a Windows or Internet Explorer out there, and we’ll see you at the next blog entry.

Monday, December 4, 2006 10:10:46 AM UTC  #    Comments [0]Trackback
# Thursday, January 5, 2006

For anyone that has been using the Beta 2 and the new final release (Visual Studio 2005 Professional Edition) version 8.0.50727.42 (RTM.050727–4200) using the Microsoft .NET Framework Version 2.0.50727, I am afraid that I may have some bad news for you and for the team that released this version at Microsoft.

The symptoms of the bug that my IDE was experiencing when I was using the Beta 2 version was exactly the same as what Scott Hanselman said here. This would now be the third complete manual uninstall and reinstall of the new final release (Visual Studio 2005 Professional Edition) version 8.0.50727.42 (RTM.050727–4200) using the Microsoft .NET Framework Version 2.0.50727, and the usual started happening again:

The certain keyboard keys became non-functional such as the enter key. arrow keys, ctrl, alt, backspace, and shift keys ?!?!

NONE of the .NET Framework tool modules would load, or “the referenced assembly could not be loaded” ?!?!

The answer is some what trivial with ONLY 20/20 hind site vision after the source of the problem was identified. Your user setting file for Visual Studio 2005 some how corrupted itself during the installation or IDE loading process, and you must have the environment reset your user data file “again, which we all know should have been tracked and eliminated in the Beta 2 version.”

Quite certainly, the last time I checked we are all still human, including Microsoft, and we make mistakes. Even so, while the product was in Beta 2 version, I believe that knowledge of this problem existed way before the RTM date of the final release and SHOULD HAVE been taken care of. In stead we see this sort of thing propagating to the next version which sort of, kind of, just so happened to be a final release. I can already see the maintenance cost going though the roof…

Any who . . . to fix this nasty bug, close Visual Studio 2005, go to the root install folder for your version of Visual Studio 2005 and enter the following commands:

cd C:\<<install root folder>>\Microsoft Visual Studio 8\Common7\IDE\

devenv.exe /ResetUserData

or if provides yet another unexpected nicety use:

devenv.exe /?

command to uncover exactly what switch option will reset the user settings file and YOUR DONE!

To be quite honest, without reading a post like this to get the solution, you will probably think that your development environment is totally and utterly useless.

Hope this helps, now get back to work!

Thursday, January 5, 2006 11:10:04 PM UTC  #    Comments [1]Trackback
# Saturday, June 25, 2005

Upgrading Dasblog turned out to be more challenging than I had originally anticipated due to, once again, not precisely following the instructions as clearly defined by Scott Hanselman's and Brian O'mare's instructions (link soon to be posted) for the upgrade to version 1.7.

More precisely, I neglected to use the new web.config for version 1.7 that contains the code that implements the new features that come with 1.7 such as the referral spam blocker and the capatcha comment robot blocker. To me, these are the two most important new enhancements in version 1.7 dasblog. Low and behold, with the correct web.config written over the old one, all the features actually work.

Saturday, June 25, 2005 1:56:47 AM UTC  #    Comments [1]Trackback
# Monday, April 11, 2005

I've really got to hand it to the people over at Acer Inc., They've truly out done them selves with their brand new, just recently released Acer Travelmate C303 Tablet PC, of which I can now say I'm finally the proud owner of.

For the Intel Centrino processor it's packing (not to mention a complete list of other compiled goodies that made this absolutely irresistable), this thing is POWERFULL when compared to some other tablet pc's I've been checking out over at Toshiba such as the Portégé or the Satellite.

Monday, April 11, 2005 10:50:59 PM UTC  #    Comments [2]Trackback
# Friday, November 19, 2004

Today I solved a major snag that's bugged me for serveral weeks. Although it was cool being able to finally plug my cell phone to my pc for internet, that nothing compared to not having the correct info to set up rights for remote development.

Well after today, that has all changed. After reading some fairly important msdn articles here, I found the rather important fact that all remote developers must have accounts on the web server in question, and if it is a Windows box, everyone must be added to the VS_Developers local machine users group. If you've ever had a similar experience, would you please send me an email or post a comment? Thanks!

Friday, November 19, 2004 6:15:09 AM UTC  #    Comments [0]Trackback
# Saturday, October 23, 2004

For those of you running WIN XP SP 2 and you are using FTP for your projects, make sure you follow these steps to keep from near tearing your hair out if you use internet explorer to access your FTP server:

Under the tools->internet options->advanced Tab:

1) Make sure that you have “Enable folder view for FTP sites” enabled/checked !

2) Make sure that you have “Use Passive FTP (for firewall and DSL modem compatibility)” unchecked/disabled !

If this saved you several hours of time and you're running win xp sp2, please comment here! I'd love to hear your comments of what has and has not worked for you with the SP 2.

Saturday, October 23, 2004 8:55:02 PM UTC  #    Comments [0]Trackback
# Sunday, August 8, 2004

For the day or so, one of our computers at home was unable to use https or ftps secure server for a short while. As a result of googling on the subject, I've discovered that if you use internet explorer, there are exactly three critical settings that must be properly set to use SSL secure sockets through the internet explorer client browser:

Under the Tools -> Internet Options -> Advanced Tab:

  1. Use SSL 2.0
  2. Use SSL 3.0
  3. Use TSL 1.0

All must be checked. Time wasted trying to figure out why I couldn't fill out online orders, 34 minutes. I suppose I could've gone to Microsoft's Knowledge Base, although I didn't feel that becoming lost among the “man pages” unix style (but managable) support pages, settings tinkering seemed to be more on my side.

Sunday, August 8, 2004 6:44:11 AM UTC  #    Comments [1]Trackback