Re: Compile Only

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



"Robert Morley" <rmorley@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:OtBrIdVrHHA.1380@xxxxxxxxxxxxxxxxxxxxxxx
At this point, .NET would be a downgrade. Never mind how I feel about
.NET in general, the primary client of my DLLs is an Access app...I doubt
I'd get anything like the performance I'm getting now by running it
through Interop. It already needs a little re-design work because of speed
(or lack thereof) issues...going through Interop on top of that would be a
nightmare.

I don't think I would recommend dot net for this, although if it's the start
of an upgrade to dot net then it could work ok.

As for the double-clicking, that's one more click than clicking on the
Compile button in Access to be brought to the next problem, or copying the
Run with Full Compile to a button in VB6. (Though admittedly, in .NET,
you're not re-compiling each time you double-click.) I was hoping for
identical functionality in VB6, perhaps through some back-door method, but
it seems it's not to be had. :) Still, since I'm dealing with DLLs for
the most part, the fact that it tries to run isn't usually a major
concern.

The main advantage is that you have a list of errors. Double clicking or
single clicking is minor.

VB.NET...then I actually tried .NET and that idea was immediately
scrapped.

Why?

Besides, as I understand it, getting VB6 to run on Vista presents a few
problems...getting .NET to run on Vista is either impossible or at least
very difficult, depending on the version.

No that I've heard of.

Since my company isn't known for using the latest & greatest (which is
odd, considering it's the main telecommunications company in our region),

The bigger the company the older the products they use it seems.

I'm forced not to port to .NET at this point. I *do* have the future to
think about here, and oddly enough, that dictates that I use the older VB6
until a) .NET matures and b) I have access to a version of it that can
work reliably on all OS's (if I decide to use it at all).

What problems are you talking about with .net and vista? AFAIK, the only
issue is you can code in dotnet 1.1 on vista but apps compiled with it will
of course run.

Michael


.



Relevant Pages

  • Re: Compile Only
    ... the primary client of my DLLs is an Access app...I doubt I'd get ... Compile button in Access to be brought to the next problem, ... "ToDo" statements appear on or near those errors if it used to be a VB6 ... telecommunications company in our region), I'm forced not to port to .NET at ...
    (microsoft.public.vb.general.discussion)
  • Re: Vista Kicking my Buttocks...Weird problems
    ... Internet Explorer®, Windows services, and third-party applications to ... Connecting an application with API entry points exported by DLLs is ... You didn't do your home work, and you didn't do any testing it seems on the Vista platform to ensure that yiur solution worked. ... As a software developer, you need to understand what is happening to program viable solutions for Vista. ...
    (microsoft.public.windows.vista.general)
  • Re: PowerBASIC
    ... the ease and versatility of writing DLLs that compile with no ... compiles are really compact and fast. ... Designer and it is very good, although the available controls and such are ... PB allows to bypass some limitations of VB6 (pointer arithmetics, ...
    (microsoft.public.vb.general.discussion)
  • Re: Unzipping without external DLLs?
    ... FSO is a bad idea in any situation. ... still out there) and see if it's translatable to VB6. ... :> I"d like to unzip a zip file without using any external DLLs. ... Sub Compress ...
    (microsoft.public.vb.general.discussion)
  • Re: Adding a reference to a COM in VS2008
    ... You know there are many features Vista has that are not know from a software developer's or computer user's standpoint on how Vista is protecting the O/S like Virtualization being one. ... For my own personal computer usage, I'll never go back to XP, and I await to see what else is being implemented in Windows 7. ... Connecting an application with API entry points exported by DLLs is something usually handled by the operating system loader, but these types of malware infection don't get the benefit of the loader's services. ... This hasn't posed a problem for malware on previous versions of Windows because for any given Windows release, system executable images and DLLs always load at the same location, allowing malware to assume that APIs reside at fixed addresses. ...
    (microsoft.public.dotnet.general)