{"id":1096,"date":"2001-06-28T05:23:58","date_gmt":"2001-06-28T05:23:58","guid":{"rendered":"http:\/\/www.soulhuntre.com\/items\/date\/2001\/06\/28\/were-gonna-try-something-different-very-different\/"},"modified":"2001-06-28T05:23:58","modified_gmt":"2001-06-28T05:23:58","slug":"were-gonna-try-something-different-very-different","status":"publish","type":"post","link":"http:\/\/legacyiamsenseiken.local\/2001\/06\/28\/were-gonna-try-something-different-very-different\/","title":{"rendered":"we’re gonna try something different – very different"},"content":{"rendered":"
we’re gonna try something different<\/b><\/u> – very different<\/p>\n
The last three hours have been very interesting. <\/p>\n
For the project were hoping to launch in the next few days I have been
\nwriting quite a bit of code. while doing some reading it became clear that most
\nof the code that I was working on would soon be obsolete if I didn’t begin
\nworking with the next version of the software. <\/p>\n
Rather than have to redo my work in the next few weeks I decided to do the
\nupgrade now rather than wait. We don’t actually have a whole lot of free
\ntime at the moment but we also don’t have the time we would need to rewrite my
\nwork over again in a week or two. So upgrade we did.<\/p>\n
Probably at 2:30 AM or so we began the process. First I had to That’s when the fun really started.<\/p>\n As it turns out the new version of ASP.NET doesn’t in fact match 100 percent After digging around on the net I found all the changes I needed to make and Anyway the really different part of all we’re doing right now is that I’m not
\nuninstall the development
\nenvironment<\/a>, then I
\nhad to upgrade the operating system, then put the development system back in. \n<\/p>\n
\nwith the old syntax. Quite a bit of the code that we used to run some of
\nthe web sites we’ve run here was quickly rendered unusable. This
\ndidn’t actually come as a big surprise, a quick look on the net before I did the
\nupgrade showed me that this was a probable outcome. In fact it was because
\nof this that I decided to do the upgrade now instead of waiting till later when
\nit would be even more painful. <\/p>\n
\neven though the new code that I was working on this afternoon isn’t working and
\nI do in fact have the old code running just fine. <\/p>\n
\ntyping this entry. The Microsoft
\nOffice XP<\/a>
\nspeech recognition system is doing the work for me. This is actually
\npretty cool, I had tried to use
\n
\nDragon Dictate<\/a> in the past and it just didn’t really have with talked to do
\nthe job . As always it seems if you can throw as much money under problem
\nas Microsoft<\/a> can you
\nwind up with something that those with supposed to do. <\/p>\n