That is:
 In AssembyInfo.cpp I've wrote
[assembly:AssemblyVersionAttribute("1.5.3.0")]
But after compile in dll properties window there is no Version tag.

I found it's not possible.
But if I have a function which is called by every forms,
do I have to copy the function to every form class?
It looks like non-sense.

I have just installed VS2005 RTM on a machine that has *never* had any
of the beta versions. It did have VS2003, but I uninstalled that.
I built a DLL with the new managed C++ syntax. The linker generated a
manifest, so far so good. The manifest says that there is a dependency

I understand that VS.NET is supposed to compile native Win32 apps that
do not require the .Net runtime.  If that's the case then there is
something else from the VS200x package that is required.
MSVCR80.DLL and MSVCR80D.DLL are present and accounted for in

Lets say I have a method called "listen_proc" inside "class1". There is
another method called "start" in the same class that has to start the
"listen_proc" inside a new thread. I am using CreateThread but I cannot
manage to pass the right function pointer, the compiler keeps on ...

I am working on a legacy code. Following is a line of the code which
complies with Visual C++.NET 2003 but not with Visual C++ 2005:
for ( int i = 0; i < (const)(X.size()); i++ ) {}// X is an object such as a
standard Vector

I am extending a legacy app that will load DLL's dynamically.  I've
worked out how to call C# DLL's from a mixed mode DLL.
Now I thought I'd delve farther into IJW and mixed mode by trying to
re-create the C# DLL in MC++.

i am working on a small MFC dialog based application.
a number of controls belongs together and i want to enable / disable them
together.
i thought i'd use a group box, just as you'd do in a C# application, but i

I'm reading pixel values (RGB) from a bitmap object using function from
system.drawing namespace & vb.net (.net framework 1.1)
But I would like to make it faster, so is there any another way of reading
pixel values from bitmap objects? (some API or smthng)

I am working on a C++ project which has been developed with Visual
Studio.Net 2003. When I compile it with Visual Studio 2005, it gives hundred
of errors. Two of the strange errors are  following, which repeated in many
places:

I looked at the addresses in an 'array<>' during debug and noticed that the
addresses were contiguous. Is this guaranteed, or just something it does if
it can?
[==P==]

I'm trying to just play with managed VC++.  I just want to draw a box
on the form when it is clicked.  Here is my click event handler
System::Void Test_Click(System::Object^  sender, System::EventArgs^  e)
{

Can't call WriteProfileInt -- I get undeclared identifier.  If I
#include <afxwin.h> -- and declare it in my .h -- I still get unresolved
external.
-- Need to write to ini, don't want to write to registry --

These don't work (I'm using VS C++.NET 2005 Express with clr:/pure syntax):
ostream& operator <<( ostream& output, String^ str )
{
    output << str ; //compile error

I am writing a Win32 DLL. I want to be able to handle any SEGVs
(segmentation violations) gracefully, by using an error handler of sorts.
Currently, if a user of my DLL (typically a VB programmer) passes a null
(or invalid) pointer to my library - the entire application crashes,