I am still wandering along VS2008. And I should admit that I have reached nowhere. And then I learn this news about the launch of VS2010 at PDC 2008.
Well, being a geek, I had no other option than to check it out. :)
And here I am pondering on the new IDE. And also the new language features in VB.NET 10.
It is a CTP, granted.
I am doing a presentation on the new cool features of VS2010 and VB.NET 10 at our local .NET User Group meeting, on March 17. So, if you are interested, please swing by.
Friday, March 13, 2009
Saturday, January 17, 2009
Applying Styles on EditCommandColumn buttons
Every button looked good. I mean, according to the project standards. Every button had that blue gradient background, with bold text. Every button looked good. Except that of the datagrid's EditCommandColumns and ButtonColumns.
Mmmhh... intelligent me, I immediately got down to work and applied the stylesheet property (CssClass, that is) to each buttons on ItemDataBound event of the datagrid.
Neh, it wouldn't budge.
Ha! It could be ItemCreated.... yeah, that is it. ItemCreated. How foolish I could be? Did I forget all those days when I had these memorized in my smart brain?
Select. Copy. Paste.
ItemDataBound event handler replaced with ItemCreated event handler. It should work this time. It should!
What? It doesn't? Why? The code says to apply the stylesheet every time the row is being created. Why not?
Mmmhhh... what should be the next step?
Google!
I was right, even the most reputed forums support that I was right!
What might have happened?
I had to find out. Right-Click. View Source.
Mmmhh.... see... every button in the EditCommandColumn and ButtonColumn had the "class=" already applied... for Edit button, it was "Button_Edit", for update button, it was "Button_Update"... and so on...
And it wouldn't change even if I insist.
Open Style.css. Create a new class for Button_Edit, Button_Update... and so on.
Eureka!!
That gradient blue background.... in my EditCommandColumn buttons too...
Mmmhh... intelligent me, I immediately got down to work and applied the stylesheet property (CssClass, that is) to each buttons on ItemDataBound event of the datagrid.
Neh, it wouldn't budge.
Ha! It could be ItemCreated.... yeah, that is it. ItemCreated. How foolish I could be? Did I forget all those days when I had these memorized in my smart brain?
Select. Copy. Paste.
ItemDataBound event handler replaced with ItemCreated event handler. It should work this time. It should!
What? It doesn't? Why? The code says to apply the stylesheet every time the row is being created. Why not?
Mmmhhh... what should be the next step?
Google!
I was right, even the most reputed forums support that I was right!
What might have happened?
I had to find out. Right-Click. View Source.
Mmmhh.... see... every button in the EditCommandColumn and ButtonColumn had the "class=" already applied... for Edit button, it was "Button_Edit", for update button, it was "Button_Update"... and so on...
And it wouldn't change even if I insist.
Open Style.css. Create a new class for Button_Edit, Button_Update... and so on.
Eureka!!
That gradient blue background.... in my EditCommandColumn buttons too...
Thursday, January 01, 2009
Another New Year
Another New Year!
2008 was not a good one for me as a blogger. That's because I have not been blogging a lot lately. Have been very busy selling my old house, buying a new one, recovering from a lyme-disease attack, and settling in the new house.
Even if you (and I) don't see any comments on my blog entries, I have lot of fans (:)), known as readers :) And they complain a lot (through emails and phone) when they dont see any blog entries. And that happened a lot in 2008.
This year (its already 2009, can't believe it) is going to be a special one. A very special one. In many ways. And one of them would be blogging. Blogging about .NET and other things.
So, a very happy new year for all my readers! Come, visit this blog often. As I said, 2009 is going to be very special!
2008 was not a good one for me as a blogger. That's because I have not been blogging a lot lately. Have been very busy selling my old house, buying a new one, recovering from a lyme-disease attack, and settling in the new house.
Even if you (and I) don't see any comments on my blog entries, I have lot of fans (:)), known as readers :) And they complain a lot (through emails and phone) when they dont see any blog entries. And that happened a lot in 2008.
This year (its already 2009, can't believe it) is going to be a special one. A very special one. In many ways. And one of them would be blogging. Blogging about .NET and other things.
So, a very happy new year for all my readers! Come, visit this blog often. As I said, 2009 is going to be very special!
Wednesday, December 03, 2008
CODE CAMP 2008
CODE CAMP 2008. Its almost here!!
Yes, it's almost here!
Saturday, December 6th.
Harrisburg University Campus, Strawberry Sq, Harrisburg Downtown.
The latest schedule can be found at our .NET User Group web site. We have our regulars Dan Clark, Kevin Goff and Dani Diaz.
Its gonna be fun, I know, with lots of cool topics!
And raffles, of course :)
I am excited.
If you live in Harrisburg area or be in Harrisburg by luck on December 6th, you should not miss this oppurtunity!
See ya there!
Yes, it's almost here!
Saturday, December 6th.
Harrisburg University Campus, Strawberry Sq, Harrisburg Downtown.
The latest schedule can be found at our .NET User Group web site. We have our regulars Dan Clark, Kevin Goff and Dani Diaz.
Its gonna be fun, I know, with lots of cool topics!
And raffles, of course :)
I am excited.
If you live in Harrisburg area or be in Harrisburg by luck on December 6th, you should not miss this oppurtunity!
See ya there!
Tuesday, November 25, 2008
A practical solution to Slow VS.NET 2008 IDE
At my work, we recently migrated our codebase to ASP.NET 3.5, using VS.NET 2008 as our IDE. Needless to say, all developers were (and tosome extent are) excited. Days passed by and our hopes started diminishing. Reason? The IDE being DEAD SLOW! Our Web Project is humungous and a Ctrl-S on a file would compel us to take a break!! Believe it or not, it is that bad!
I started researching. Googling, that is :-)
And to my surprise, we were not alone in the planet. There were lot of developers going through the same pain we were having. Needless to say, it was some solace, but none of the forums, on which the complaints were pouring in, had any solid soultion. And that frustrated me!
After talking to other projects in the firm, we decided to split the web project into chunks. And this article by Scott Gu gave us courage.
We did some POCs and we think we are in the right direction.
UPDATE
The PoCs that we did have given us more courage and are comfortable in breaking our humungous solution to sub-solutions. We would have lot of happy developers... and happy developers make wonderful products!! :)
I started researching. Googling, that is :-)
And to my surprise, we were not alone in the planet. There were lot of developers going through the same pain we were having. Needless to say, it was some solace, but none of the forums, on which the complaints were pouring in, had any solid soultion. And that frustrated me!
After talking to other projects in the firm, we decided to split the web project into chunks. And this article by Scott Gu gave us courage.
We did some POCs and we think we are in the right direction.
UPDATE
The PoCs that we did have given us more courage and are comfortable in breaking our humungous solution to sub-solutions. We would have lot of happy developers... and happy developers make wonderful products!! :)
Friday, August 08, 2008
Wednesday, July 02, 2008
Disabling Menu Item
A recent post by Joel Spolsky suggests to display the reason why the menu item is not accessible by the user.
http://www.joelonsoftware.com/items/2008/07/01.html
I disagree.
The reason is, this kind of behavior would confuse the user more than disabling the menu item.
I would go with the recommended approach of hiding the menu item entirely as the user would not see the item and he would not be concerned about it anyways.
http://www.joelonsoftware.com/items/2008/07/01.html
I disagree.
The reason is, this kind of behavior would confuse the user more than disabling the menu item.
I would go with the recommended approach of hiding the menu item entirely as the user would not see the item and he would not be concerned about it anyways.
Subscribe to:
Posts (Atom)
