July 2004 - Posts
News.com is saying that there will be a new build of Win64 for x64 on Monday.
Hopefully, i'll be able to run Yukon and Whidbey on it.
4 GHz Pentium 4 is delayed till next year.
Not enough 3.6 GHz Pentium 4 chips to go around.
Some small problems with their latest chipset.
Sorry, but I can't help but laugh at this. He just sent out the “big“ memo last week and now this. I still think it is a communication problem. Sorry Dr. Barrett, but I go back to my original views on the problem. You have created an adversarial relationship with the workers in your company and you are now reaping the rewards of the relationship which you have helped create. Good Job!
BTW, I don't hate Intel nor do I think that offshore outsourcing is somehow evil. I think that offshore outsourcing is merely a fact. The problem I have had and continue to have with the view of Dr. Barrett (and others, he is merely the most vocal), is that after they tell us to look towards the high end and to get a better education, they then “pass the buck“ and say that there is no guarantee that Intel, or any other company, will be interested in hiring you. Why? Well only they know. Interesting that Intel, and other companies saying the same things, wouldn't give me the first look, let alone a second, when I graduated from college with honors with a BSEE and MSEE specializing in VLSI design and computer architectures yet these are the same companies that wanted to greatly expand H1-B and now are so hot on offshore outsourcing because there aren't enough technically competent people already in the US. Stop the double talk folks. Admit that the reason is money and let's move on.
Ok, rant over.
Have you ever heard the phrase “The more I practiced, the luckier I got?” Well, that is how I feel right now. I have been working really hard recently on some relatively simple reporting code. There is a report query page and a report output page. Due to the nature of the application, both pages are written in classic ASP and run on a Windows 2k server.
The problem has been that I have been trying to improve the accessibility of the output for screen-reader users. In the US, the term is 508 user, so it may be something different for you depending on where you are. We did some accessibility testing yesterday. While we passed just fine, I took some of the suggestions from the accessibility group and put them into my reporting code. I resubmitted the changes to the group this morning. About 1:00 pm local time, I got an email from the head of the accessibility group calling me a GENIUS! (which, of course, I am) for having researched the appropiate html output and put it in appropiately. He said that I am the only developer that in this government department to do this correctly. Not only did this note go to me, but it went to several people further up the org chart here. This can't hurt! I hope that this is remembered when I ask for more money in the future.
Why is the fact that this guy sent this out so amazing? Well first off, no one ever says anything good about anyone else. That is just human nature. The big issue though is that the first time I ever set down with this group, by the end of accessibility exam, they looked like the village people from an old 1930s horror flick where they are coming after the monster with pitchforks and torches. I barely escaped with my life. By the time that I had gotten back over to my group, the project manager had already recieved a call about all of the accessibility problems with the application (an app that I took over from someone else). While I can't fix a lot of the problems due to budgets, I have made sure that my new code is as accessible as possible.
Today, I got the payoff for all the hard coding time. I worked hard, practiced hard, developed hard, and I got lucky. Funny how it all goes together.
First Whidbey Beta 1 doesn't work with the build available on MSDN. According to the newsgroups, it only works on this magical mystical build 1184 that only official testers have.
Then Yukon Beta 2 only works on a build after the magical 1184 build.
Now this, Win64 for x64 won't see the light of day till sometime next year as a released product. http://www.eweek.com/article2/0,1759,1628259,00.asp
What is someone to do with a AMD64 bit system that won't run Whidbey or Yukon.
It seems that Dr. Craig Barrett of Intel is upset with his employees. I disagree with his views, but I couldn't resist responding to his latest memo with a smartass comment of my own.
Perhaps he should use the native language of his employees to get his point across.
A new build of the .NET 2.0 Framework has been included with Sql Server 2005 Yukon Beta 2. This appears to be an incremental release with merely some framework bug fixes. The build number goes from something like .16 to .42 according to the newsgroup posts that I have read today. Unfortunately, I have not seen this myself. I am mentioning this because I have read this in one or two newsgroup posts. Your mileage may vary. If you have installed the beta 1 of Whidbey, you will need to uninstall the framework before performing a new install of Yukon beta 2. This information comes from the publically available newsgroup microsoft.private.sqlserver2005.relationalserver.clr on the MS NewsGroup Server at http://communities.microsoft.com/newsgroups/default.asp?icp=sqlserver2005&slcid=us. Enjoy your reading and adventures with Sql server 2005 Yukon Beta 2.
According to the article listed below, Yukon will be available today to MSDN Universal and Professional subscribers.
If you create a CLR Object in Whidbey with the VS.NET IDE and then try to deploy it in Sql Express, you will want to make sure that you are looking at the Output Window when you perform the deploy. If not and you get an error message in the lower left hand corner saying "Deploy Failed," you will be left wondering what in the heck is going on.
I just wrote some CLR Objects with C# in Whidbey Beta 1 and Sql Express. I had a couple of methods named the same thing and I was going to use Method Overloading to call them given the parameters that I handed in. I compiled and everything was fine. I tried to deploy to my Sql Express database, and bango, multiple methods with the same name are not supported. Is there any “good way” to simulate method overloading in Sql Express / Yukon?
Appologies if this has already made the rounds. Thanks to Kent Tegels for including this in his signature.
If you want some additional samples for Sql Express Express, check out:
More Posts Next page »