Interview Questions in ADO.Net hi friends Any one send frequently asked Important questions in C# .Net, ADO .Net, Asp .Net and Sql Server. . . . . . . . tx in Advance. . . . . . Hi, Find this. . (B is concept of Boxing and Unboxing ? (B) What is the difference between VB.NET and C#? (I) what is the difference between System exceptions and Application exceptions? (I)What is CODE structure’s? (B) What does virtual keyword mean? (B) What are shared (VB.NET) / Static(C#) variables? (B) What is Dispose method in .NET? (B) What is the use of “Overrides the finally block execute? (A) What is Indexer? (A) Can we have static indexer in C#? (A)Can two catch blocks be executed? (A) What is the difference between System.String get response text? (B) How can we send request to the server using the XMLHttpRequest component? (I) How do we pass parameters to the server? (I) How can we create a you explain the concept of triggers in ‘UpdatePanel’ control? (I) Can you explain the ‘UpdateProgress’ component? (A) How can you do validations in Ajax? (A) How do we do exception handling smoothly CLR has CTS (Common Type System).Example in VB you have “Integer” and in C++ you have “long” these datatypes are not compatible so the interfacing between them is very 21 Microsoft introduced Common Type System. So “Integer” datatype in VB6 and “int” datatype in C++ will convert it to System.int32 which is datatype of CTS.CLS which is covered

Can C component Talk to C# component? Hi, Can anyone tell me that what is the relationship between C and C# component?Can both these components can communicate in any way?also what is COM Callable Wrapper(CCW)? Thanks Yes C and C# component can communicate. hi, COM Callable Wrapper When a COM

alone, in my opinion, sells the book - because it represents the most extensive discussion of C-based DLL's, exports, imports and class types I've seen in any book. Troelson Meaning in Life" explanations. After 50 pages of Chapter 1, you'll be building a C# callback client and ready to embark on the COM odyssey. Chapter 2, "The Anatomy of Support, Interface design and Binary Compatibility. Of course you are in either Visual Studio 6 C++ or Visual Studio 7 C++ when going through this chapter. Troelson completes this with examples of VB 6.0 COM 8 with more detailed intermediate - level topics such as COM Variant handling, Variant wrappers, SAFEARRAY, C-Style arrays, param arrays, structures, collections - and even connection points. No book I know of particularly like since you can build free threaded .NET class libraries, provide them with a CCW, and have legacy apps and even Classic ASP use your .NET stuff and be blissfully and handling overloaded methods. You'll finish up by building both a Visual Basic and C++ COM client. Chapter 11, "COM - to -.NET Interoperability - Intermediate Topics" goes into even more detail this and the coverage is extensive. Personally, I try to avoid using COM+ and Serviced Component architecture because of the potential performance hit, but I still think it's useful and

calling .Net assemblies from COM client using a COM Callable Wrapper. A COM Callable Wrapper (CCW) exposes .Net objects to COM. This allows extension of Com based application without re-writing includes the lack of Intellisense and object browsing. To overcome these limitations control of the CCW is required. This means writing the interfaces as well as the interop classes. This requires Browser make the effort worthwhile. A Gotcha One item I noticed in working with the CCW is the behavior with arrays. For demonstration a Concat method will be added that takes code compiles and runs successfully. [DispId(2)] string Concat(ref string[] strArray); Summary Using a CCW can help extend life into existing Visual Basic 6.0 applications. This can save considerable following: • Do explicitly create the interface. This provides the greatest control and robustness of the component. Using the _ as the interface prefix follows the pattern used by VB 6.0 of .Net to extend the functionality of VB 6.0 applications. Jon Wojtowicz is a C# MVP and a Systems Analyst at a large insurance company in Chattanooga, TN where he as a consultant working with Microsoft Technologies. This includes ASP, COM, VB6 and .Net, both C# and VB.Net since Beta 1. He has been an MCSD since 1999 and an

Here is one article from MSDN that takes about Interoperability in .Net. There is a C#.Net online dictionary, but not full-fledged. It covers some basic terminolgies. Please have a between .NET and COM environments. For example, runtime creates an instance of COM Callable Wrapper (CCW) when a COM client accesses a .NET component. In the same way, an instance of Runtime Callable Wrapper (RCW) is created when a .NET client accesses a COM component. These wrappers abstract the differences and provide the seamless integration between the two environments. Along costly affair as far as memory is concerned. Here nice article for you http: / / www.c-sharpcorner.com / UploadFile / akchavali / Interoperabilityin11282005052912AM / Interoperabilityin.aspx Hi here is the website for all the technical words used in .net http: / / www.c-sharpcorner.com / UploadFile / akchavali / Interoperabilityin11282005052912AM / Interoperabilityin.aspx Hope it helps you. Create New Account keywords