[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 245
  • Last Modified:

.net technology support for distribution?

what is the .net technology support for distribution?
0
she1
Asked:
she1
  • 3
  • 3
1 Solution
 
RonaldBiemansCommented:
Could you explain a little more ? Do you mean setup en deployment ?
0
 
she1Author Commented:
in j2ee, we have ejb or rmi to support the distribution,
how about .net?

thanks
0
 
The_BiochemistCommented:
In most versions of visual studio you have the ability to create setup and deplyment projects. These use the project output from your application to create an executable which you can distriblute. The executable created is used by the newer versions of MS installer to install the appllication thereby giving the user the 'recognisable' installer interface. It also gives you the ability to 'bootstrap' the .net framework installation onto your installation in order to ensure the users have the correct framework installed.

0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
she1Author Commented:
i mean some object like ejb that support distribution,
is it the com+ or ?

thanks
0
 
The_BiochemistCommented:
Right, Sorry, hadn't quite got what you were after.

The EJB thing for java looks like it handles threading, security, resources etc... and seems to be comparable to the .Net framework.

The .Net framework handles the majority of the interaction needed with the operating system and is simply a collection of classes you can reference in your code thereby getting the underlying functionality. It has a set of base classes which cover collections, diagnostics, drawing, IO, Forms, Communications, threading and more with multiple subsets of each of these.

As far as a comparison with COM it is essentially the next generation of COM but in the same breath nothing like COM. It is a completely new archetecture where Windows and the COM architecture are wrapped in a series of fully managed classes giving a great deal of abstraction and making it much easier to program as most of the hard work has been done for you. It uses something called the common runtime language which makes it's use independant of the language used e.g. VB, C++, C#, VJ#, Jscript are essentially all equal.

Also with projects like MONO you can port many project directly to linux giving a multiplatform dimention.

For more information see:

http://msdn.microsoft.com/netframework/default.aspx
        ----> General information (.Net framework developers site)

http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.dotnet.framework&tid=e84f018d-e933-489d-adac-fc63e7c43ad8
         ---> Discussion on .Net vs Java applets

0
 
she1Author Commented:
from your explaining:

ejb->ejb container
com+->.Net framework.

.Net framework offering the container service like resource pooling , transaction,

i am not sure if i am right.

thanks
0
 
The_BiochemistCommented:
Yep your on the right lines.

The framework handles all of those types of things that you are used to having handled for you... memory allocation / removal, resource pooling, threading and thread pooling, interactions with the core windows kernals.

(forgive the niaevity of my java knowledge) from the little I know of java to use it you have to download a special package that puts an icon of a coffee cup in your task bar and handles the 'behind the sceens' stuff. When programming you use lots of pre-written objects that interact with that application.

The .Net framework has runtime elements that in essence are very similar and are installed when the .net framework is installed these handle the 'behind the sceens' bits. The installation also installs lots of fully managed classes, the framework base classes, which are essentially the .net version of the objects used in java which you can incorporate into your code.

So com+ and com objects are not used at all when programming a truly .net application.

It is all about layers of abstraction between the old unmanaged windows and COM environments and your code with a consistant managed set of base classes.

e.g. This is the kind of hierachy utilised.

Your Code
       |
        -----> Common Framework classes (imported into your code as needed to use the code and very comprehensive functions they contain etc...)
                       |
                       -----> ASP net / Windows Forms (Generation of the user interface in either web apps or windows apps respectively)
                                       |
                                       -----> Data and XML (data access and storage - all based natively on XML)
                                                     |
                                                      ----->Base Class Library (Core components inherited by common classes - all aps based on inheritance of these classes)
                                                                   |
                                                                   -----> Common Language Runtime (Handles memory management, garbage collection, threading...)
                                                                                             |
                                                                                              -----> Windows and COM+ (so COM+ does exist but highly abstracted and only as part of windows.)

I hope that makes some more sense and explains how the parts of teh framework fit in.
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now