Rants Tagged with “Microsoft”
<< < 1 2 3 4 5 6 > >> (Total Pages: 6/Total Results: 57)
I was startled to see the new MS home page. I really like the new look. Especially as it relates to consumers. Good work guys...
Is it just me or does LA suck for conventions? Oh well, its still a 'must' to attend. So I would expect that Yukon/Whidbey will ship by the PDC (or at the PDC). What will the big topics be at this PDC? Probably Avalon/Indigo. Oh yeah, that was last PDC ;)
Evidently MS slipped on thier pledge to deliver the betas at the conference. This article implies that they are claiming that the betas are “imminent“...wonder what that really means? Q3? Q4?
UPDATE: Evidently the article is wrong about the VS.NET Beta...hopefully the Yukon beta isn't far behind.
How I wish I were there. Evidently the Yukon Public Beta and the VS.NET 2005 Beta will be available. Get them while they're hot!
For all attendees, skip the Heiniken Museum...you're gonna want to remember this convention! TechEd will be very “lekker” this year.
I've been dealing with this nasty ASP.NET Configuration Error that only happens on my dev machine for several weeks now. Inexplicably, it will think that some random DLL that is part of my project is locked while it is trying to do the aspx compilation. I finally found the solution in the MS Support Database; the solution? Disable the Indexing Service (or exclude the ASP.NET temporary files section). Arg! The problem seems to be when my build copies a copy of a .dll to the temporary files section, it would start to be indexed by the Indexing Service and was locked so that the aspx compilation couldn't overwrite it.
For those who might think they have this problem, these are the symtoms (and click on the link for the solution):
- Random “Configuration Errors“ in your ASP.NET that say “Access Denied to XXX.dll“
HTH
I've had the WinHEC build of Longhorn for a while now and I have to say I am very pleasantly surprised. It seems that Longhorn is really coming along. I am very focused on WinFS programming, so I have not had too much time to dig into other interesting topics like Avalon (though Chris Sells loves the data binding) and Indigo.
The biggest change that has effected me is the lack of VS.NET. Because of very different development schedules, there is not a version of VS.NET that works with this release of Longhorn. At first I was a bit daunted...I have become so dependent on the tools. I haven't compiled from the command-line in quite a while. Luckily, MSBuild came to the rescue. After having been using NAnt, I was unsure what the big deal with MSBuild was and why it mattered. I am now a big fan. Instead of having to learn their XML syntax, I was delighted to find out that it will build based on a csproj file. This helped me out a lot, because I know how to write those files like the back of my hand (mostly from hacking csproj's to fix annoying problems like licx files remaining after you remove a reference).
Once I could build, I started digging into WinFS, I am suprised by the sheer scope of change in this version. I do expect it to calm down in later builds and I know it is *really* early. What has surprised me is the pace of development by the WinFS team. Whole interfaces have changed drasticly and concepts (chielfly relationships) seem to be redesigned completely. Truth be known, I am not sure it is for the better yet; much of the interfaces for navigating relationships seem much more heavy handed and complicated...but I have faith they'll get it right before it is all over.
Lastly, though I would never expect it from an early OS, the startup/shutdown time in this version is vastly improved from the PDC bits. Since I am dual booting to Longhorn, this really helps me switch back and forth quickly.
I just ran across a great new tool for searching my outlook messages. I have kept messages going back over four years so searching has become a fiasco. Luckily
LookOut for Outlook as come to the rescue. It is in beta at the moment so I have no idea how much it'll cost, but so far I am very impressed. Once it indexed my messages, it was lightning quick. The indexing in the background didn't bother my day-to-day operation of Outlook either. And finally, since it required the .NET framework, I can say that I am glad that it is written in .NET. Check it out.
I like it when a “MS v. Some small guy” story works out. Mike Rowe has given MikeRoweSoft.com to microsoft, but in return he's getting some great stuff. Here's what Microsoft is doing in return for the domain:
Agreed to help direct any traffic from mikerowesoft.com to Rowe's new Web site (which he's currently working on) to make sure he doesn’t lose any business. The company will pay any out-of-pocket expenses related to this change, including cost associated with changing over to the new url and any other expenses. (The Rowe family is now calculating those expenses.)
Invited Mike and his family on to the Microsoft campus for the company's Microsoft Research Tech Fest in March. The company will pay for the travel and accommodations. No promises, but it's possible he could meet Bill Gates, depending on the Microsoft chairman's schedule, Desler said.
Agreed to pay for Mike to get Microsoft Certification training. Depending on which courses he chooses, this could lead him to become a certified support technician, or system administrator, or something along those lines.
Agreed to give Mike a subscription to MSDN, the Microsoft Developer Network Web site, with various tools for developing software around Microsoft products.
Agreed to give Mike an Xbox game system, complete with a number of games of his choosing.
A cheeky seventeen year old has incurred
Microsoft's wraith. Mike Rowe decided to start a website, MikeRowSoft.com (say it in your head)...very funny...
I don't get this either. A video IPod? How much disk room would it take? How much would it cost? Maybe someone else see's the point...I don't.
