Archives
-
Five AM and all's well...
*WHEW*
-
Thanks Jesse
Jesse's been a big help to me over the past few days. Not only has he provided the code to a really awesome part of the IDE, which is the inspiration for a killer new project I'm working on, but he's also come up with a way to provide your own stylesheet for the WebLogs. I am now also using his sheet, although I will be experimenting with my own version when I have the time. At this point, that will be sometime in the early 20's.
-
Following Through On My Promises
A few days ago I promised to blog about MS' recommendations for versioning in .NET. Well, while visiting my .NET Resources link, I came across this article, and I don't think I could have written it any better. Check it out, and be sure to browse those resource links... there's good stuff in there.
-
Remapping ASP.NET Runtime Versions in IIS6
Earlier last month I saw someone complain that you could no longer use aspnet_regiis in Windows Server 2003 running IIS6. Having just repaved both my employer's and my personal machine to run WS2K3, and installed VSNET2002 and VSNET2003 SxS, I can gladly say that this is not the case.
-
WELCOME TO THE WEBLOGS @ ASP.NET
WOO HOO. .NETWebLogs... Now hosted by the ever popular Microsoft, who as of today, kissed and made up with AOL. Scott has done a fabulous job with the WebLogs, and it's great to be on the most popular .NET website on the Internet. Scott, keep up the great work, and I'm looking forward to this continuing to be the single best resource for .NET information by the people who use it every day.
-
Component Versioning Proposal
I'm working on an article (well, one of several that I am currently working on) about how to handle versioning in .NET. This is sparked by several threads about handling Framework versions, and my experiences with Xheo beta testing their components. Paul Alexander and I have a great relationship in regards to the software we write. Neither one of us has fully taken advantage of the situation we created for ourselves, but hopefully that will change in the very near future.
-
More Chocolately VB Goodness
Talked with Joe Feser today. Man what a freat guy. He's a frickin smart guy too. Informs me that he's finishing up the next version of VB XML Comments Creator (I think it needs a new name tho =) ). Yes, that's my logo for GenX.NET in the corner. I need to clean that logo up a bit and send him a better copy.
-
Feedback Desired
In further thinking about GenX, I wanted your opinion. Do you think that a .NET utility that has nothing to render should still have design-time support? Personally, I don't think that it should, but I've been wrong before and I'd like to hear what you think. Please send me an e-mail or leave me some comments and tell me what you think.
-
My love affair with DotNet continues
In my ever-continuing quest for knowledge, I have been toying with an idea in my head about rewriting GenX.NET (my flagship ADO.NET Exporter component) to make better use of the OOP techniques that .NET has to offer. This would be the third major rewrite of the component. The first time I told Brady Gaster about it, he said "Why not use an Interface?" For Brady, that kind of thing is a no brainer. He used to program Java for Wells Fargo, and now he's probably one of the greatest C# coders I've ever seen. The way he cranks the stuff out just boggles the mind.
-
Early & Adopter ROCK
Courtesy of my hereos, those guys who redefine bleeding edge, you can now add WMI to the Server Explorer in VS.NET 2003. Gosh, ANOTHER reason to switch??!? I dunno... <wincing> I think I should stick with 2002.
-
Death of the Consultants...
Consultancy.... R.I.P.? ZapThink seems to think so, at least, according to News.com. Well, I am construing it just a bit. What they actually said is that, with the advent of Web Services, consultants have to focus less on getting systems to communicate, and more on, God forbid (or Allah as the case may be) Business Process Rearchitecture. This is long overdue in my opinion.
-
Need I say more?
What kind of sexy are you?
he he he ;). Yep, that's me :). -
Rescinding earlier comments...
I'm not going to put any more effort into trying to solve the "framework compatibility" problem that was discussed, because after talking with some people over at MS (thanks RobH and Scott Louveau) I've decided to stand by my original statement. The only responsible thing that control developers should do is have a build for each version of the Framework. I don't want my 1.1-compiled app trying to run on 1.0, and you shouldn't either. You want to give your users the best experience possible, and by only providing one version, you are not doing so. I will blog about a few possible solutions that MS suggests within the next day or so, but I agree with them and their recommendations.
-
Coding on drugs...
Ever tried coding on Nyquil? It's quite an experience. You should see the code I came up with while working last night. Actually.... scratch that. I'd rather not embarass myself about it.
-
Taking the Initiative
I'm taking the initiative, and creating a "Combating Framework Hell" Task Force to solve the issue of being unable to programmatically redirect assemblies to use different versions of the Framework. Anyone who is interested, please reply to this post or use my blog form to contact me.
-
"Framework Heck" Interpretations and Community Responsibility
Frans seems to be getting awfully riled up over the backlash from his post. I can say this because I had this lesson taught to me as well: As a developer blogging in this community, you have a responsibility to clarify what is opinion and what is fact. What Frans effectively did is back up PeopleSoft's horrendously ridiculous comment that .NET is IT asbestos. By saying "ISV's: do NOT upgrade to Visual Studio.NET 2003! " you are sending not only a bad message to the community, but a message of opinion masked as fact. If versioning issues are your only reason, (pardon my bluntness) sorry but IMO, your reason is not good enough to justify such a harsh stance. The reason I can say anything about this is because I have been guilty of this before, and have since had to change my thinking.
-
NEWS BULLETIN
Chris Sells ceases to make fun of VB developers. Also, Moon spins off into outer space. Film at 11.
-
*sigh*
Unfortunately my idea for rerouting assemblies to 1.0 programmatically does not work. The problem is that there is not currently a way to unload an assembly (to the best of my limited knowledge). If you could, what I would do is prevent it from trying to unload the referenced assemblies and load the 1.0 assemblies instead.
-
C# Design Patterns
Scott doesn't like "C# Design Patterns". I can't say that I do either. It was horribly written and very hard to follow. I will be looking into Slavomir's suggestion very shortly.
-
Has anyone
tried out my code yet? I'd really like to know if it works.
-
.NET 1.1 Issues Continue
Frans Bourma comments on the issues he has with VS.NET 2003, and even goes as far to say that if you are an ISV, you should not be building tools to .NET 1.1. Wow. That's a pretty rough statement. Well, I'm an ISV and I upgraded to VS.NET 2003 six months ago, and while it means that you have to exert a little more effort, the improvements alone are worth it.
-
OK Day, Better Evening
I was looking through the pingbacks/trackbacks in my blog, and I found out that there are over 100 links to my quasi-rant on how .NET 1.1 is not an upgrade to .NET 1.0. WOW. That's kinda cool. Scoble's pretty popular, and he only has 16 readers
. I think those same 16 read my blog, because all the rest are Google links. -
Edit While Debugging in VSNET2002
Go to Tools... Options, then click the Debugger folder, select Edit and Continue, and make sure both checkboxes are checked for C# and VB. This way you can edit ehile debugging and not have the debugger get pissed off. You can also set whether or not the debugger will restart execution, warn you, or ignore the changes and continue debugging. One step close to Edit and Continue in VB..... still waiting tho.
-
Community Petition
This is a petition to get our community members that have been assimilated, <ahem> ROB HOWARD and SCOTT GUTHRIE, to blog more often. To sign, please enter your name in my comments. Lets see if we can't get them to dish out more dirt about what's going on in Redmond.
-
b0rg lovers across the globe cheer!
SCO moves to sue all Linux users. 'Nuff said.
-
Why I think dynamic queries are an extremely bad idea
I've been thinking about this for several days now, and I have finally formulated an opinion about the whole "dynamic query" argument. I'm going to throw my hat into the ring and give you my two cents.
-
Cool new skin for Trillian
I cannot express enough the coolness of Trillian. Don't get me wrong, the new Windows Messenger 5 beta is pretty nice, and MSN Messenger 6 will kick butt, but you can't beat being signed into 5 different screen names at once. If you're active in the .NET community at all, it pays to make use of it. As you'll see in the screenshot, the ability to nest groups and rename contacts can be invaluable.
-
DANGER WILL ROBINSON
WARNING!!! Do NOT use Frontpage 2003 to edit user controls. It thinks it's an aspx page and tries to add the @Page Directive to it, killing the control. It does this right before saving, so if you delete it it will just put it back in again.
-
Architecture Happiness... well not quite
I'm so excited. In one of my fits of retardedness, I got upset because the database table names in one of the website components I'm building collides with the table names from another app. I was lathering up in the shower, all worried about having to recompile and re-deploy to three sites, I remembered that my architecture allows me to only have to confine the changes to the Data Layer. Man I love 5-tiered architecture.
-
Passion is a GOOD thing
Paschal noted that I insense passion in people. Some may take that negatively, but I think it's a good thing. Why? Because most people could care less about anything, and if I can create an intense desire in someone to speak their mind, and God forbid, maybe even care, then all the better.
-
Hold on to your hats
It's finally here! My new article on the Windows 2003 Platform Wave. Grab your surfboard and hand on, cause this ain't your mother's dry humor. My wit and sarcasm go unedited for the first time, so you'll get a good look at why Early & Adopter are my heroes. There is a heated discussion going on about it as well, so go check it out.
-
Speaking of Geek Movies..
Saw X2 on Friday. I've never seen a more culturally-relevant movie. Want proof? Check this out.
-
PLEASE
...delete your blog tool test posts. Do you leave tracing on when you deploy a website? Then please don't leave the main feed messy.
-
In case you couldn't already tell...
I was out pretty much all last week, buried with 5 different projects that all had to be finished (surprise surprise, none of them are yet), but I've been taking some time to catch up on my blog. I wanted to bring a couple of things to your attention.
-
Lies!
So I didn't have to be in the Top 20 in HS after all... Don't you hate it when you're lied to by authority figures? My guidance counselor should be ashamed of herself.
-
Please Note:
I was NOT accusing Sean and Scott of actually smoking weed. I love reading their articles because they have inanimate objects such as Win2k3 and the Framework talking to themselves. Not only that, but they create these funny personalities that just somehow fit the object. I was just commenting that most people are only this funny when they're high, and Early & Adopter can accomplish it minus toxic carcinogens.
-
From the "You Should Have Known That Already" Files...
No wonder I work better when the radio's on....
-
More news from Early & Adopter
Further proof that combining an MS Beta ID and weed is a bad idea. I know they don't roll doobies with their whitepapers, but most people have to be high to be this funny.
-
Move over Sean & Scott..
Neo's takes the ranks as the coolest early adopter. (Sorry guys, you couldn't keep that trophy forever.) I wonder if he's tried out Windows Server 2003 yet.