January 2004 - Posts
BLOGGERS LAW: The Introduction clause:
Lest you be another voice in the wilderness.net; please trumpet your arrival with something cool that makes us all think you are a genius and someone worth listening too.
For example, say: “I am Joe Blow and I am the Program Manager for the Foo team at Microsoft, just to prove this I will tell you something about Foo that will blow your mind!”
Follow this statement with something really cool that we might all care about and voila - you have instant syndication success :)
#region Disclamer
/*
This is not a political post in any way. I have been researching some site load issues lately and found it interesting to look this data up considering the traffic these sites are surely seeing at this point in time…
*/
#endregion
Dear Mr Presidential candidate, as a techno-geek there is something that is important to me; what is your platform? I mean, what are you running on…and how will you serve the internet people…?
George W Bush (georgewbush.com)
Windows 2000, IIS – ASP.NET!
John Kerry (johnkerry.com)
RedHat Linux, Apache 1.3.27, Python variant
Howard Dean (howarddean.com)
Linux variant, Apache 1.3.29, PHP 4.3.4
John Edwards (johnedwards.com)
Linux variant, Stronghold
Wesley Clark (clark04.com)
Linux variant, Apache 1.3.28
Joe Lieberman (joe2004.com)
FreeBSD, Apache 1.3.12
Dennis Kucinich (kucinich.us)
Linux variant, Apache 1.3.27
Al Sharpton (sharpton2004.org)
Linux variant, Apache 2.0.40
Earlier I made a post about the prefix given to server controls and Robert commented that he did not like the fact that you could not specify the same prefix for controls hosted in different assemblies.
If you ask me this only makes sense because there is a true physical distinction between the controls being that they are in different assemblies and the fact that the system forces this to be represented in prefixing just makes good sense. However, his comment got me thinking about various control vendors who sell multiple asp.net controls. In a lot of these cases, I may want to buy 3 of their 7, not all and this while not really problematic; it is not elegant for my perspective in that now I have 3 different assemblies.
Enter ILMerge coupled with a little engineering and a component vendor could roll composite assemblies for customers in an ala carte fashion. I pick the three components I want, give my visa number and their purchasing pipeline fires off an ILMerge process that creates a single assembly with just the componentry I wanted.
I know, I know – you can do this already. Modules are one way, having different build profiles another - there are a number of ways…Just thought this would make cool use of ILMerge and then Robert would not be able to complain about his different prefixes because his controls would be composed all in one assembly.
I have noticed a number of server controls people have put together lately, some commercial but most free on places like Code Project that always render out with the generic tag prefix. It occured to me that the control of this is not readily obvious so maybe I should be kind and point out that you can change this. Lets suppose I was a commercial control vendor named 'Some Company' and wanted to have the prefix 'soc' for my server controls. I would use something called the TagPrefixAttribute to force this behavior. By placing this code in my AssemblyInfo.cs file I get the desired affect.
[assembly:System.Web.UI.TagPrefix("SomeCompany.ServerControl", "soc")]
OK, not earth shattering but it is the little things that can help distinguish a good control from a great one.
Never really cared until I realized I was repeating the same old task over and over, and I love to automate that type of situation.
The graphical query analyzer tools has some command line switches that can enable to you launch, login and go to a specific db in one fell swoop.
You can do other stuff with the switches; setting input files or file lists as well as output files.
For example: isqlw –S(yourserver) –d(Database Name) –E(Trusted Connection)
More Posts