You are currently browsing the category archive for the ‘programming’ category.
I am diving head-first into the world of .NET 3.5. And not having the support of my employer, I am flying solo, using the Express versions of Visual studio.
I ordered this, and hoping it will be a promising reference for me.
Pro C# 2008 and the .NET 3.5 Platform, Fourth Edition (Windows.Net).
Update (10/23/2008):
Well 
No I wonder my next step. Apress has two C# ASP.NET books and I am not sure which one to get. There is a Pro book and a Beginners book.
Pro ASP.NET 3.5 in C# 2008, Second Edition (Windows.Net)
They both have good ratings but I wonder if the Pro version will just be more information that I care about and may skip over some basic things I don’t understand about web UI design. On the other hand the basic book may be too basic and not add any “meat” to its explainations. I don’t learn as well if I don’t understand why something is doing what it is. I guess it’s time for a trip to the bookstore and flip throuh some pages. I wonder if my family will ever let me out to do that…
Not sure on the accuracy of these, but I needed this info, found it, and wanted somewhere to stick it.
| File Ext: | Content Type: |
| docm | application/vnd.ms-word.document.macroEnabled.12 |
| docx | application/vnd.openxmlformats-officedocument.wordprocessingml.document |
| dotm | application/vnd.ms-word.template.macroEnabled.12 |
| dotx | application/vnd.openxmlformats-officedocument.wordprocessingml.template |
| ppsm | application/vnd.ms-powerpoint.slideshow.macroEnabled.12 |
| ppsx | application/vnd.openxmlformats-officedocument.presentationml.slideshow |
| pptm | application/vnd.ms-powerpoint.presentation.macroEnabled.12 |
| pptx | application/vnd.openxmlformats-officedocument.presentationml.presentation |
| xlsb | application/vnd.ms-excel.sheet.binary.macroEnabled.12 |
| xlsm | application/vnd.ms-excel.sheet.macroEnabled.12 |
| xlsx | application/vnd.openxmlformats-officedocument.spreadsheetml.sheet |
| xps | application/vnd.ms-xpsdocument |
Thanks to:
Doug mahugh, on msdn blog
//Get response HttpWebResponse response = (HttpWebResponse)request.GetResponse(); StreamReader sr = new StreamReader(response.GetResponseStream()); result = sr.ReadToEnd(); sr.Close(); Console.WriteLine(result);
As I log into My Yahoo! account I am greeted with a message that a new updated version of My Yahoo! site is available as a beta site. Since Yahoo! usually lets you go back to the old version again, I thought I would check it out. Basically it has become the typical AJAX’d to hell big font “Web2.0″ site. Fooy. I don’t get the new interfaces with all this Javascript, big-ass fonts, and bubbly edges, they are just such bloated pigs. The new font resolutions make it really difficult to use anything but a full-screened browser, which I hate to do. The UI is windowed for a reason. The My Yahoo! beta reminds me a lot of the new mail interface Yahoo! designed a few years ago. No I don’t use it either, it was just to slow and clunky of an interface back then, though I haven’t tried it again. Another part that irked me is that many of the modules I had on My Yahoo! page no longer worked on the new site. Why would you offer a new layout if many of the items which are used, aren’t available any longer? I don’t get that.
FogCreek Software’s FogBugz has done the same thing with their latest release, 6.0. Changed to this really fat font and some other layout changes. I understand UI changes always take some time to get used to, but even after three weeks using the product, it still doesn’t feel natural. Funny, reading Joel Spolsky’s blog, when he returned to New York after his first demo tour for FogBugz 6.0 he himself the UI has been stripped down way to much and it’s just horrible. It happens, anyone in development knows it. At least he is being smart about it and re-doing it from step one.
I have to say that I am happy that so far Yahoo! hasn’t forced me into using their new interfaces for their products. I don’t think that I am that stubborn when it comes to changes, I just expect at least to have the same functionality that I did in a previous version. Don’t make me take two steps backwards in functionality when you introduce a new product.
I would really like to know why web designers are thinking this new larger font is the way to go on web pages? I am seeing it more and more, and I still find it less appealing and usable.
I have used Sourcegear’s Vault for about 3 years now at work. I have recently started a project on my own and, of course, want to use a SCM. I decided to try Perforce, since the product if free for two users and five work spaces. Well, I just didn’t get it, I figure I just not smart enough to use the product. I couldn’t even submit the intial load of the repository without having to read the manual. The one thing that really turned me off, it that I had to check out a file to edit it. When I forced to overwrite the file anyway, Perforce didn’t noticed that it changed. I am sure I wasn’t doing somthing properly, but these are issues I never had with Vault. I grew up in the world of CVS, where everyone has there own copy of the codebase and are responsible for incorporating the latest changes from the repository before checking in there changes. So you are probably asking why I just didn’t use Vault? Simple enough, I wanted to try something different. So I have, I am not that crazy about it, and I am going back to Vault, which by they way is free for a single user also. The one thing I will say about Perforce over Vault is that it seems much less system intensive and has less hardware requirements.
