EnC with VS 2005 Std SP1
kris
I had VB 2005 code working in EnC mode. But after harddrive crash, I have
installed SP1 but my code no longer works for EnC mode.
Please help.
PS: If I create new project I can do EnC.
Thanks,
kris
Mike Williams
news:Oyt7nFEP...@TK2MSFTNGP03.phx.gbl...
> I had VB 2005 code working in EnC mode. But after
> harddrive crash, I have installed SP1 but my code no
> longer works for EnC mode.
What's VB2005? It is definitely not Visual Basic . . . at least not the
*real* Visual Basic. Is it one of the aliases of "the imposter" which
Microsoft keeps changing the name of in order to confuse people? Sounds like
it might be. No wonder your hard drive crashed, after loading all that stuff
;-)
Mike
Karl E. Peterson
kris
> Time to upgrade to VB6!
> --
Are you serious?
Michael C
> >
>> Time to upgrade to VB6!
>> --
>
> Are you serious?
Unfortunately yes, he is
>
>
Galen Somerville
>> --
>
> Are you serious?
>
I would giess that you are in the wrong newsgroup with that VB2005 crap.
Galen
Jeff Johnson
> I had VB 2005 code
--
[Canned response]
This is a VB "classic" newsgroup. Questions about VB.NET (including VB
2005/2008 and VB Express, which have dropped .NET from their names) are
off-topic here.
Please ask .NET questions in newsgroups with "dotnet" in their names. The
*.vb.* groups are for VB6 and earlier. If you don't see the *.dotnet.*
groups on your news server, connect directly to the Microsoft server:
msnews.microsoft.com.
For questions specific to the VB.NET language, use this group:
microsoft.public.dotnet.languages.vb
Please note that things like controls and data access, which have their own
subgroups in the Classic VB hierarchy, are not language-specific in .NET, so
you should look for groups like these:
microsoft.public.dotnet.framework.windowsforms.controls
microsoft.public.dotnet.framework.adonet
(Note that "vb" is not present in the group name.)
Robert Morley
especially VB.NET, is almost universally despised (we have a grand total of
*two* VB.NET proselytizers that I'm aware of). That was why Karl responded
as he did.
One reason for our distress is the complete and utter lack of a migration
path that doesn't involve enormous amounts of work. (We won't mention the
pathetic excuse for a migration wizard that VB.NET offers; it seems you end
up with more TODO lines than lines of code!) Another reason is the speed,
or complete lack thereof compared to VB6, though I gather VB 2005 has
managed to address this somewhat. And finally, of course, there's the whole
"managed" environment. What if I want to program in VB, but don't want to
be "managed"?
This is just a very broad overview of a few of the chief
complaints...complaints that Microsoft has never deigned to address, since
in their minds, VB is just a "toy" language, for kids & hobbyists, that no
"serious" programmer would ever want to use.
As you might've gathered, this is NOT a universal vision by those of us not
located in Redmond, so we're rather irritated by MS, and don't trust them
not to pull this kind of crap again. It has caused a number of defections,
including my own (at least in my personal programming...work is another
matter), to other--more stable and self-compatible--languages. One of the
most common that I've heard is Borland Delphi, but there are plenty of
others.
So despite the moderately signfiicant new linguistic features of VB.NET,
many of us still perceive it as a downgrade overall and therefore refuse to
migrate. I'm still on the fence, personally, in terms of whether I'll
migrate my work applications to VB 2008 or some other platform when the time
comes. Being data tiers and the like, they may well get ported back to
Access, where they originally came from. I guess we'll see whenever the
need arises. For the time being, however, VB6 is quite capable of filling
my requirements for the foreseeable future, and I know many others in the VB
groups feel the same way.
Rob
"kris" <k...@k.com> wrote in message
news:%235CNHwF...@TK2MSFTNGP02.phx.gbl...
Karl E. Peterson
>> Time to upgrade to VB6!
>
Read my sig, d00d. What part don't you get?
Jeff Johnson
news:13lvrkm...@corp.supernews.com...
>> I had VB 2005 code
>
> --
> [Canned response]
> This is a VB "classic" newsgroup.
Argggg. I have GOT to start checking the newsgroups line.