![]() |
Tuesday, March 04, 2003 |
Source: [ShowUsYour-Blog!] Dan Wahlin's done it again... he's posted 4 excellent Windows Media movies that show a simple example for getting started with WSE In it learn how to:
12:23:34 PM ![]() |
Source: [ShowUsYour-Blog!] Last week I purchased the MS MCAD/MCSD Self paced training kit for 70-310 and 70-320. I'd been kind of browsing the first 3 chapters which cover the framework (overview) and building windows services. Deep down I knew that I hadn't really been learning anything as I've been too busy reading other cool stuff:
Anyways, yesterday a friend asked me a couple of simple questions about services, such as how to debug them and what the various security contexts that they can run under refer to. After much head scratching I had to admit that I wasn't terribly sure. Last night was a solid night of reading and, needless to say, I'm feeling much more comfortable with Windows Services. Bring on Serviced Components!!! References: 12:21:43 PM ![]() |
Source: [ShowUsYour-Blog!] I am the Framework. I run managed code. I am without flaw. (repost). Had an interesting experience today; a friend sent me an assembly and asked me to check it out. I referenced the assembly in my application and starting writing some elite code that consumed it. Project compiled fine but when I executed the app. it blew up and complained that assemblies couldn't be found - System.Xml in particular. Welcome to SxS ( side by side execution ). What my friend had failed to tell me is that his assembly was built on Version 1.1 of the framework and I only have Version 1.0 installed! Thankfully this fine article - http://www.3leaf.com/default/articles/ea/SBS.aspx - told me how to rectify the problem by adjusting my configuration settings to map to the V1.0 assemblies. Here we go again :D
Note: here is an example of the error you can expect to see if you get caught by this: File or assembly name System.Xml, or one of its dependencies, was not found.Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
12:18:43 PM ![]() |