Liam Leane of google c sharp groups has answered these questions and these are her answers
Wrox booxs are always the best reference books for any language i have
come accross so good choice :-) I will answer those which i have run
> pg xxviii of introduction there is a mention of the putting the
wrappers across COM components how is that done in the .NET?
Have a read of
explans both coming from COM and coming from c#
> What is a rich client application?
A standard website is a thin client. A control / component / assembly
/ browser extension that is downloaded and then talks with some
website (usualy via a webservice) can be described as a rich client.
Basicly the idea is that the majority of the work is done on the
client pc rather then the server (so you write your c# but instead of
it running on a website via aspx it is downloaded via a browser and
run on a client machine and then it talks to your server to get
whatever data it needs) http://www.richclients.org
In short avoid at all costs, they are pure evil and will remain so
until Longhorn becomes the standard. In addition you are limiting your
users to windows only with the correct version of the framework
> pg xxix says security info is stored in the asssembly how to use that
in the code?
describes it very
well. If you are dealing with windows apps this is very important but
on the web side it becomes alot less so.
> pg xxix says data can be imported from the windows platform to the
other platforms, how to do that?
Couldnt spot what exactly said that but .net supports webservices and
all ODBC compliant databases out of the box. If you mean code
portability to other platforms there is ongoing projects such as mono
to allow this.
> pg xxix says different of the assemblies can be used in the same
does it mean two same named assemblies with different versions can be
added as reference to the same code?
Do you mean the bit that talks about different versions existing side
by side? That is actualy referencing the GAC (accessable by browsing
to c:\winnt\assembly) You can keep as many versions of the same
assembly as you want in there so you can make partial upgrades to
applications (IE Application A needs version 126.96.36.199 of Assembly A but
Application B needs version 188.8.131.52)
> pg xxix talks about the self contained assemblies what is the
advantage of using them in the code?
Encapsulation, Modularisation, Code reuse, the list goes on forever
> pg xxix how important is the registry for the c# developer, where
will he use it?
Never ever ever ever ever ever. All web apps have a web.config file
and you can define all your settings for the application in there. All
windows forms / console apps have an app.config that serves the same
> pg xxx there is a mention of the staging server, how to use it? is it
a free download of the microsoft website?
Staging server is a term in enterprise development. Typicaly you have
your development environment (where you write your code), your QA
environment (where your code is tested as part of the whole), your
staging environment (where the client can see your code as part of the
whole) and your production environment (where your release code sits)
> pg xxx what is use of the ODBC data provider and how is it different
from the System.Data and System.Data.SqlClient?
ODBC data provider is a generic ODBC library for .net. SqlClient and
OracleClient are specific to the types of ODBC server and thus support
a great range of features.
> pg xxxi by side by side execution, will the system have two different
versions of .NET running at the same time. Still confused with wo
different versions running at the same time how can one build the two
different solutions at the same time?
No, this means you can have two different versions of the .net runtime
installed (for example i have 1, 1.1 and 2 installed)
> pg xxxiii how is the type safety implemented in .NET?
Same way it is in msot other OO languages, you have strings, ints etc
and they have to be comverted to fit in to each other (although lots
of this is done for you so you can do things like string s =
> pg xxxiii how r pointers and direct memory access implemented in C#?
C# is memory managed, you dont need to worry about this
> pg xxxiii what r user defined attributes?
You will come accross portions of code where you get code like:
public class greap.Web.Content.Data
The first line is an attribute in .net speak (nto to be confused with
an attribute in UMl speak) and it allows code to be executed when
something is used. you can define and use these. THis is very
important in AOP (http://aosd.net/
> pg xxxiii what is the difference between the executable and library
of .NET components?
One has a .dll extension and can't be directly run and the other has a
.exe extension and can be run
> pg xxxiii what are machine cycles and how to track them in c#?
> pg xxxiv what is an active directory?
Users & Groups system used by MS within NT based domains
> pg xxxv what is the advantage of the using the object pooling,
message queing and transactions in COM+?
Allows for ASynch processing and transactional services
> pg xxxv how to write the windows services?
> pg xxxvi Regvcs BookDistributor.dll [COM+AppName] [TypeLibrary.tbl]
what does it mean?
Committed to be a consistent geek