C#

DataGrid in simple english

Raju — Thu, 22 Sep 2005 14:28:00 GMT

http://www.dotnetjohn.com/datagrids.aspx

NGen 2.0 persistant native code image generating tool features.

Raju — Wed, 14 Sep 2005 17:44:00 GMT

NGen, will create persistent native code to speed up process time.

Usually JIT (Just In Time) compiler will compile the MSIL ( Microsoft Intermediate code) to native code immediately before code is executed, this is temporary, this is redundant processing time, to reduce this nGen is used.

a) nGen will create native images.

b) These will be stored in native image cache.

c) When assembly is used by a managed application, CLR loader will locate, load and use the native images.

Drawbacks of nGen 1.0 and 1.1

a) All managed assemblies have dependencies. even if only dependency is on mscorlib.dll.

b) nGen Images contains code and data structure which are based on assumption on dependencies of the assembly.

c) If dependencies change, it invalidates code in the native image and runtime will fail to use native image instead reverting to JIT compilation.

d) This problem is particularly bad when considering that if a component shared by many applications is updated, for instance System.dll, then this will cause the native images for many applications on the machine to be invalidated.

e) Native images could be used only in single application domain in a process.

Features of NGen 2.0

a) Instead of invoking NGen on individual assembly, in 2.0 it is invoked on application, This is done by running NGen on top level assembly in the application.

b) NGen will automatically discover the dependency assemblies and make sure that all are having images (applies only to static assemblies recorded in assemblies manifest, dynamically loaded assemblies are not discovered by NGen like Assembly.load).

c) NGen keeps record of all dependencies of application, so that if shared component is later updated NGen can discover all application which are affected with the update and regenerate images wherever needed.

d) NGen is now windows service.

e) You can submit to NGen que if application is large enough, it will find run on free system time.

f) NGen 2.0 created images can now be shared across application domains in a process.

g) Reflection is fully supported only in native images.

h) New Generic features are fully supported.

When to Use:

1) When native images are created, these will be directly loaded by CLR and JIT is not required so the amount of space taken by JIT will be saved for other purpose.

2) Native images are loaded by CLR as just like any other DLL, which makes it possible to have cross domain usage of native images, and if other application using these native images does not require loading again, instead use already loaded image.

Extra cost:

a) You need to identify the accessing of number of times on module boundary,.

b) Strong Named assemblies which are not in GAC will have extra cost on validation, which causes every page to be touched in native image.

Article on Paging with repeater control in ASP.Net

Raju — Tue, 06 Sep 2005 12:41:00 GMT

Paging with Repeater control in ASP.NET

http://www.charon.co.uk/content.aspx?CategoryID=28&ArticleID=21

Webbased MS Word dynamic document generation in C# using HTML tags with hidden tables.

Raju — Wed, 27 Jul 2005 19:02:00 GMT

Here is the dynamic MS Word document generation in C#, You can use HTML tags and style sheets,
In this example table is designed not to appear even in non printable view. Usually tables will appear in word though they will not be seen when printed, In this example I have changed the border font color to white so as not to appear even in grey color, You can see MS specific style sheet tags:

HttpContext.Current.Response.Clear();
HttpContext.Current.Response.ClearContent();
HttpContext.Current.Response.ClearHeaders();
HttpContext.Current.Response.Buffer =true;
HttpContext.Current.Response.ContentType="application/msword";
HttpContext.Current.Response.Write(@"<!DOCTYPE HTML PUBLIC ""-//W3C//DTD HTML 4.0 Transitional//EN"">");
HttpContext.Current.Response.AddHeader("Content-Disposition","attachment;filename=InvDetails.doc");
HttpContext.Current.Response.Charset = "utf-8"; //UTF8
HttpContext.Current.Response.ContentEncoding = System.Text.Encoding.GetEncoding("windows-1250"); //windows-1250
HttpContext.Current.Response.Write("");
HttpContext.Current.Response.Write(" ");
HttpContext.Current.Response.Write("<Table border='1' bgColor='#ffffff' borderColor='#ffffff' cellSpacing='0' cellPadding='0' style='font-size:10.0pt; font-family:Verdana; background:white;border-collapse:collapse;border:none;mso-border-alt:solid white .5pt;mso-border-right-alt:dotted white .5pt; mso-padding-alt:0in 0in 0in 0in;mso-border-insideh:.5pt dotted white; mso-border-insidev:.5pt dotted white'> <TR> <TD width=300>");
HttpContext.Current.Response.Write("MY First Row First cell Data");
HttpContext.Current.Response.Write("</Td><TD>");
HttpContext.Current.Response.Write("My First Row Second Cell Data");
HttpContext.Current.Response.Write("</Td></TR><TR><TD width=300>");
HttpContext.Current.Response.Write("MY Second Row First cell Data");
HttpContext.Current.Response.Write("</Td><TD>");
HttpContext.Current.Response.Write("My Second Row Second Cell Data");
HttpContext.Current.Response.Write("</Td></TR></TABLE>");
HttpContext.Current.Response.Write(" ");
HttpContext.Current.Response.Write("");
HttpContext.Current.Response.Write("UnderLined data");
HttpContext.Current.Response.Write("");
HttpContext.Current.Response.Write(" ");
HttpContext.Current.Response.Write("");
HttpContext.Current.Response.Write("This is paragraph data which can be placed in single line, when it appears in word it will have autofit. Today's date in specific format::");1
HttpContext.Current.Response.Write(String.Format("{0:d-MMMM-yyyy}", DateTime.Now));
HttpContext.Current.Response.Write("");
HttpContext.Current.Response.Write("");
HttpContext.Current.Response.Flush();
HttpContext.Current.Response.End();

Here it ends...

dotNet DataGrid article list

Raju — Tue, 19 Jul 2005 17:02:00 GMT

http://www.datagridgirl.com/articles.aspx

Top Ten Tips for WebService Interoperability

Raju — Tue, 28 Dec 2004 18:00:00 GMT

http://weblogs.asp.net/smguest/archive/2004/08/12/213659.aspx

Good tips on interoperability between .Net and Java webservice, it goes on with defining datatypes in XSD, using NUnit, JUnit for testing, tracing, Date and time comparision , sending differnt datatypes - datamismatch and avoiding null values with sending arrays types, its good on its brief, it has valuable points in Feedback section.

UML more experienced from SCott W. Ambler

Raju — Thu, 07 Oct 2004 16:30:00 GMT

Scott W. Ambler, is cool on experienced stuff , he describes what's best to use in different aspects using all components of Rambugh methods and with other models.

http://www.agilemodeling.com/style/

Highlights could be

--> Author is more specific on language, which is very cute thing, while using auto code converters this could help a lot.

eg: Public attributes and functions of an interfaces is yet not supported by Java language, while if we put class diagram interfaces with these, this diagram may not be used for this language.

--> He puts a barriage between the thinking interms of class idenitfication,
(responsibility-driven and data-driven)
--> A class could be created with attribute and operations (behavior)

--> on other aspect , it could be created with logical aspect like responsibility driven with an exaple as the Invoice class is responsible for providing its total,
and other things or operations will be help this responsibility.

Read more here:
http://www.agilemodeling.com/style/

Mark of Polymorphism

Raju — Tue, 27 Apr 2004 20:05:00 GMT

In one of technical discussion with friends, different topics were discussed, there was a point on Polymorphism, one of those feels, Polymorphism is not of use and debate continued.

His supporting points are

Polymorphism is to have common name for similar type of functionality and for different data types and arguments.

a) How do we know that which data types a function/procedure it supports?

b) Even if I know, the function name is not self explanatory

a. Eg: add(int, int) , add(double, double)

Which could be easily expressed as addInteger(int, int) and addDouble(double,double).

I could say polymorphism has been included as a flavored item, to increase the list in OOPs, for advertising.

Is this so?????

Date Time localization work around solution

Raju — Mon, 19 Apr 2004 18:58:00 GMT

Work around solution on date time localization:

http://blogs.msdn.com/brada/archive/2004/04/13/112784.aspx

Time 00:00:00, As this is serialized and sent over a timezone this date could be changed to be the previous day, with a time of 23:00:00. If this user then logged into the system in the other time zone they would now see their birthday as being a day earlier and they would complain it was incorrect

Product team comments:

This is an issue I have seen a few times before.
For V1.0 and V1.1, There is a work-around for XML Serialization. You can indicate in the schema that the DateTime is a Date only. If you start from schema, you should use xsd:date primitive type, to change the object model you can use custom attribute on the member:

[XmlElementAttribute(DataType="date")]
public DateTime date;

[XmlAttributeAttribute(DataType="date")]
public DateTime date;

Notice that this will not work for DataSet or SOAP Serializer.

Another work around is to call ToLocalTime() on the DateTime before serializing and ToUniversalTime() after serializing. This is sort of cheating because it is not really a UTC date, but it should make the time zone adjustment go away.

In a future release we do have planned a solution that is similar but not identical to what you have requested. You can mark a DateTime instance as Local, UTC or Unspecified, and Unspecified means that it should not be serialized with a time zone. Unfortunately it won't magically take effect because it would break compatibility. But there will be ways to opt-in to this behavior for DataSet, XML Serialization and XML Convert.

Static Class - Abstract does not require inheritence for full implementation.

Raju — Mon, 19 Apr 2004 12:21:00 GMT

Here is good discussion on Static and abstract, Max has given this example in Ericqu comments section on static class blog.

@Talbott
abstract does _not require_ inheritance for a full implementation:

abstract class Foo
{
static void DoSomething(){}
}
...
Foo.DoSomething();

is totally legal code. 'abstract' only means no instance can be created - at least at the view of the Compiler/Runtime.
But I have to agree that most people think 'abstract' means an incomplete class. So it may be less confusing to introduce a "new" keyword instead.

http://weblogs.asp.net/ericgu/archive/2004/04/13/112274.aspx