How to include or Add Referance with VC++ 2005?
-
Hello im working with MSMQ , so i want to make dll that will send to MSMQ, so how can i include MSMQ Library (System.Messaging.dll) in VC++ ? C:\WINNT\Microsoft.NET\Framework\v2.0.50727\System.Messaging.dll thanks
you can use #using directive to include the managed dlls into your code. Then use the namespace declaration and create the class instance. See the sample below.
#using <system.messaging.dll> using namespace System::Messaging; if ( !MessageQueue::Exists( queuePath ) ) MessageQueue::Create( queuePath );cheers..milton -
you can use #using directive to include the managed dlls into your code. Then use the namespace declaration and create the class instance. See the sample below.
#using <system.messaging.dll> using namespace System::Messaging; if ( !MessageQueue::Exists( queuePath ) ) MessageQueue::Create( queuePath );cheers..milton -
you can use #using directive to include the managed dlls into your code. Then use the namespace declaration and create the class instance. See the sample below.
#using <system.messaging.dll> using namespace System::Messaging; if ( !MessageQueue::Exists( queuePath ) ) MessageQueue::Create( queuePath );cheers..miltonProject Properties -> configuration Properties -> General -> Common Language runtime support set-->Common Language Runtime Support (/clr) but also it gives me this error: :doh: Error 1 Command line error D8016 : '/MTd' and '/clr' command-line options are incompatible cl how can i fix it please ?
-
Project Properties -> configuration Properties -> General -> Common Language runtime support set-->Common Language Runtime Support (/clr) but also it gives me this error: :doh: Error 1 Command line error D8016 : '/MTd' and '/clr' command-line options are incompatible cl how can i fix it please ?
Error 1 Command line error D8016 : '/MTd' and '/clr' command-line options are incompatible '/MTD' is the Multithreded C Runtime debug version. That means you chose an unmanaged project type. What kind of project you are working on ? If you need to call .net libaries from an unmanaged type, best way is to wrap all ur bussiness rules into an assembly and use CCW - Com callable wrapper to invoke the wrapper .net component from ur unmanaged app. Or else change the project type to a managed. rgds...milton.
-
Error 1 Command line error D8016 : '/MTd' and '/clr' command-line options are incompatible '/MTD' is the Multithreded C Runtime debug version. That means you chose an unmanaged project type. What kind of project you are working on ? If you need to call .net libaries from an unmanaged type, best way is to wrap all ur bussiness rules into an assembly and use CCW - Com callable wrapper to invoke the wrapper .net component from ur unmanaged app. Or else change the project type to a managed. rgds...milton.
actually i created my project with VC6++, the Convert and open project with VC2005, emm ok i will try to open new fresh project from 2005 directly , so i have to open managed dll project from vc2005. can you tell me which option when i want to create project give me managed dll ? currently i make win32 project--->dll with puting sign on Export symbols only. is im in right way ? -- modified at 17:42 Saturday 6th May, 2006
-
actually i created my project with VC6++, the Convert and open project with VC2005, emm ok i will try to open new fresh project from 2005 directly , so i have to open managed dll project from vc2005. can you tell me which option when i want to create project give me managed dll ? currently i make win32 project--->dll with puting sign on Export symbols only. is im in right way ? -- modified at 17:42 Saturday 6th May, 2006
i think yes im in safe side :-D, now i can compile with no errors after set Common Language Runtime Support (/clr), i want to know if there is any changes between dll on vc6++ and vc2005, everytime i call function within dll by using this declaration int _stdcall SendToQueue(char * SBody,char * SLabel) { return 123; } and i have to make .def file and write exported function header inside it so it will work with vc2005 or there is problem with it ?
-
i think yes im in safe side :-D, now i can compile with no errors after set Common Language Runtime Support (/clr), i want to know if there is any changes between dll on vc6++ and vc2005, everytime i call function within dll by using this declaration int _stdcall SendToQueue(char * SBody,char * SLabel) { return 123; } and i have to make .def file and write exported function header inside it so it will work with vc2005 or there is problem with it ?
You were in the wrong side. you again choose an unmanaged project type because win32 project is an unmanged type. After all what you need is to call MSMQ APIs right? You can do it in two ways: 1) Either use unmanaged MSMQ Apis 2) Or use Managed .Net class libraries, which is the one you chose. For the first option: you can go for an unmanaged project type. ie it can be a vc++6 project or a VC++8 MFC application. Then for accessing the MSMQ apis go thru http://www.thecodeproject.com/w2k/msmq.asp. This method will be fater as MSMQ apis are unmanged and you are directly dealing with the apis. Second option is to use managed dlls: This is the option you chose, by using System.Messaging.dll. This is not that good as the previous one as it wrapes the actual MSMQ COM Apis under the hood. If you want to go for this option yu can do it in the following ways: a)Use an Unmanaged VC++ app and use interop for calling the wrapper u created on managed System.Messaging.dll. For this you have to create one managed wrapper dll (New project --> Visual C++ -->CLR --> Class library) and wrap all your msmq requirements using System.Messaging.dll functions.Then use COM iterop to use this managed wrapper dll from ur Unmanaged VC++8 application. (Or you can avoid wrapper dll by using CorBindToRuntimeEx(), but more complicated. better dont go for this if u r beginner). b)USe a Managed VC++ application (New project --> Visual C++ -->CLR --> Windows forms applicaion / Class library). This is a c++/cli application. This will be the easiest methed if you are planning to use System.Messaging.dll (in C++) instaed of the MSMQ COM apis. Or another choice is, you really want to go for vc++? if you go for C# and System.Messaging.dll then it will be the easiest of all. more questions are welcome ...milton
-
You were in the wrong side. you again choose an unmanaged project type because win32 project is an unmanged type. After all what you need is to call MSMQ APIs right? You can do it in two ways: 1) Either use unmanaged MSMQ Apis 2) Or use Managed .Net class libraries, which is the one you chose. For the first option: you can go for an unmanaged project type. ie it can be a vc++6 project or a VC++8 MFC application. Then for accessing the MSMQ apis go thru http://www.thecodeproject.com/w2k/msmq.asp. This method will be fater as MSMQ apis are unmanged and you are directly dealing with the apis. Second option is to use managed dlls: This is the option you chose, by using System.Messaging.dll. This is not that good as the previous one as it wrapes the actual MSMQ COM Apis under the hood. If you want to go for this option yu can do it in the following ways: a)Use an Unmanaged VC++ app and use interop for calling the wrapper u created on managed System.Messaging.dll. For this you have to create one managed wrapper dll (New project --> Visual C++ -->CLR --> Class library) and wrap all your msmq requirements using System.Messaging.dll functions.Then use COM iterop to use this managed wrapper dll from ur Unmanaged VC++8 application. (Or you can avoid wrapper dll by using CorBindToRuntimeEx(), but more complicated. better dont go for this if u r beginner). b)USe a Managed VC++ application (New project --> Visual C++ -->CLR --> Windows forms applicaion / Class library). This is a c++/cli application. This will be the easiest methed if you are planning to use System.Messaging.dll (in C++) instaed of the MSMQ COM apis. Or another choice is, you really want to go for vc++? if you go for C# and System.Messaging.dll then it will be the easiest of all. more questions are welcome ...milton
i think it works with option : b)USe a Managed VC++ application (New project --> Visual C++ -->CLR --> Windows forms applicaion / Class library). This is a c++/cli application. This will be the easiest methed if you are planning to use System.Messaging.dll (in C++) instaed of the MSMQ COM apis. -------- Thank you Milton finally its works :-D
-
i think it works with option : b)USe a Managed VC++ application (New project --> Visual C++ -->CLR --> Windows forms applicaion / Class library). This is a c++/cli application. This will be the easiest methed if you are planning to use System.Messaging.dll (in C++) instaed of the MSMQ COM apis. -------- Thank you Milton finally its works :-D
had gone for a short hiking to Wachusett Mountain MA. Just back now. sorry for abt the delay buddy. Be aware that the option u selected is managed c++ (c++/cli) app and not a typical vc6++ like unmanaged application. cheers..milton.