Solution
Oddly enough, something must have happened with the dotnet framework 1.1 ... I reinstalled the 1.1, and all is well again, odd how it just one day decided to not work though. Thought I would post the fix for it none the less, in case anyone else runs across this problem.
|