Re: (Raising my hand) I don't get it...
From: drayyarb (drayyarb.128ypi_at_webfrustration.com)
Date: 02/26/04
- Next message: Paul Clement: "Re: Pharse a CSV file"
- Previous message: Ron Allen: "Re: Problems with my dataset _ plz help, Urgent!!"
- In reply to: Lars: "(Raising my hand) I don't get it..."
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 26 Feb 2004 18:58:38 GMT
Lars wrote:
> *Hello,
>
> I write all my applications in VB6-- and I don't understand the
> reason to move to .NET (other than MS might break VB6 apps in future
> updates). I'm taking the position that I don't understand something,
> so I'm hoping some experienced people can clarify my
> position:
>
> I write shareware apps that I only distribute through my own website.
> Download bandwidth is a major concern because that will cost me
> money.
>
> Here are my main concerns:
> * If I create a C# app, am I including the 20+ mb CLR in my download?
> (my current zipped vb6 setup files are around 5 mb)
> * Is there a package and deployment method? (it sounds like there
> isn't, again-- cause for confusion)
> * It sounds like .NET apps are easier to disassemble, is my code at
> risk from everyone seeing it and posting cracks?
> * Does .NET run on Win95? (If not, how far back does it go? Not one
> of my strongest concerns)
>
> These are the points that keep me from making the conversion. It
> seems like .NET is not for the shareware author, but for the
> corporate enterprise and/or internet applications. I'm a happy VB6
> programmer that likes to write desktop applications, but if V
> B6 suddenly breaks in a couple years, I need to understand how .NET
> applies to my situation and how to handle it.
>
> I appreciate any insight,
> Lars
>
> PS I find the conversion difficult because I learned programming in
> VB-- no formal education in C+ or anything else. *
No the CLR is not part of the exe. The actual app files are no larger
than in VB6. As a whole they are acually smaller because you do not
have all of those nasty .ddl's to tag with your app. There is a
Setup/Deploy Project that you can add to you app project in visual
studio.net for deployment that is acually pretty good. As far as the
disassembly, I've heard rumors of that also, but supposedly, the newer
version of visual studio.net (2003) makes things more secure.
Personally, I've never had any trouble with disassembly. Again, about
the backward compatibility, if the computer has the .NET framework on
it, supposedly, it will run any .NET application. I have seen some
posts that older machines cannot run the CLR because it takes a certain
amount of memory that older machines usually do not have; never looked
into it myself really. There is no reason for you to learn any C
language. There is VB.NET. It is a little different, but not too bad
if you have a good working knowledge of VB6. If VB6 works for you, I'd
say keep using it though. The only thing you have to worry about
really is if the target pc has the .NET framework on it. Hope this
helped some.
-- drayyarb ------------------------------------------------------------------------ posted via www.WebFrustration.com
- Next message: Paul Clement: "Re: Pharse a CSV file"
- Previous message: Ron Allen: "Re: Problems with my dataset _ plz help, Urgent!!"
- In reply to: Lars: "(Raising my hand) I don't get it..."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
