Re: VB or VC++ for DirectShow programming ?

"Alessandro Angeli [MVP::DS/MF]" <nobody@xxxxxxxxxxxxxxxxxx> wrote in
message news:uWQ0PN1mGHA.2312@xxxxxxxxxxxxxxxxxxxxxxx
[...] The IDE may be more limited, but that only means you may need to do
something manually now and then to get your code done.

For what it's worth, because I didn't have access to the full Visual Studio
right when it was released, I used the Express version for awhile. For
managed code applications, it is *quite* sufficient. You'd have to be doing
some pretty esoteric stuff to require any manual workarounds. The IDE does
not limit you with respect to the actual code in any way...the only
limitations are in access to certain features such as resource editing,
possibly some debugging features, and that sort of thing. You get complete
access to the forms-based UI design (but not resource-based, such as the
non-managed menu, dialog, icon editing, etc.)

I found it surprisingly useful, considering it's a free development
environment. There are huge numbers of people out there for whom this is
the only development environment one would need.

Now if I could just get someone to point me to a complete, but intelligible
discussion of what everything manifests do and are used for. :) I ported a
DirectShow filter over to the new Visual Studio environment the other day,
and discovered that even this non-managed code was for whatever reason
required to have a manifest included with it (generated automatically by the
IDE). Now I'm starting to wonder if manifests have always been with us, but
were previously hidden by the linker or something (or called something else
that I actually know about). So far, even asking my friends who are
supposedly knowledgeable about managed code, I just get shrugs.

Pete


.

Relevant Pages

  • Re: Win DDK 3790 cannot compile with VS 6.0, but linking error with VS. NET
    ... I guess I was spoiled by visual studio where I can put Preprocessor ... Same question also applies even with DDK build.exe utility, ... >>Windows 2000 and Windows XP drivers is expected within the shipping ... >>build environment. ...
    (microsoft.public.development.device.drivers)
  • Microsoft Express Tools (WAS: c++ programming evironment)
    ... Here is a link to the Express editions for the Microsoft tools... ... If your app is a simple utility that is designed to be Windows only, then the Express editions should do the trick nicely. ... i've seen some references to the visual studio for windows. ... developer coming from a Windows environment. ...
    (Fedora)
  • Re: Startup default language in VS 8 Pro
    ... actually shows it as Visual Studio 9.0.30729.1 SP1 on the About screen, ... all of the MSDN documentation file for the installed Help content ... documentation installation which is an earlier version and is so designated ... Would using a run command that is targeted to the environment profile ...
    (microsoft.public.vstudio.general)
  • Converting VC++ 6.0 executable code to .Net DLL
    ... environment (Visual Studio 2005). ... Anyhow, the environment generated a main class for me, shown below, as ... belong to any namespace, as is just a large collection of classes developed ... What would I need to do to export my C++ interfaces? ...
    (microsoft.public.dotnet.languages.vc)
  • Re: How to create a universal .exe ???
    ... With manifests, you're not so lucky. ... corner of MSDN before they ship an exe to anyone. ... should you run everything thru a MSI installer. ... next Visual Studio produces binaries that run only when they were ...
    (microsoft.public.vc.language)
Quantcast