[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

VC++ Win32 project in .NET solution compiles as an .EXE file rather than .DLL

Posted on 2006-06-17
2
Medium Priority
?
558 Views
Last Modified: 2008-01-09
Hi,

I have a .NET solution consisting of a VB.NET Add-In project, a VC++.NET Win32 project which I'm using to store an image for my Add-In in a resource file and the Setup project for this solution.

I opened the VC++.NET's project properties window and changed its "Configuration Type" from "Application (exe)" (which was the default value when I added this projecvt to my solution) to "Dynamic Library (dll)" which is the format I need for my Add-In.

However, to my surprise, every time I compile this project I get an .EXE file instead of a .DLL file!!! I've changed the above property to a lot of different options out of curiosity and it always created the expected output format except for... DLL!!!

I tried to test this behaviour in a few test projects, and it looked like I was playing the lottery... One tested project worked and the output was DLL while a few others stuck with .EXE even if the selected "Configuration Type" was "Dynamic Library (dll)"  rather than "Application (exe)"!!!

Then, when I compile my solution (the add-in, resource file project and the setup project) at a certain point I'm getting the error message "Microsoft (R) Visual Studio registry capture utility has encountered a problem and needs to close".
If I close this message box by pressing its OK button, the setup carries on as nothing happened and compiles all three projects successfully!!!

Could anyone help?

Thanks!!!
0
Comment
Question by:sterlingdev
2 Comments
 
LVL 48

Accepted Solution

by:
AlexFM earned 2000 total points
ID: 16925962
Maybe it is more simple to create new Win32 Dll project than to convert existing exe project?
Generally, such conversion is possible. It is necessary to compare all linker and compler options in Dll and exe projects, and make required changes. But I beleive that creating new Dll us mich better.
0
 

Author Comment

by:sterlingdev
ID: 16943397
I've recreated the VC++ project directly as a DLL and it worked!
Thanks!
0

Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Real-time is more about the business, not the technology. In day-to-day life, to make real-time decisions like buying or investing, business needs the latest information(e.g. Gold Rate/Stock Rate). Unlike traditional days, you need not wait for a fe…
Hello there! As a developer I have modified and refactored the unit tests which was written by fellow developers in the past. On the course, I have gone through various misconceptions and technical challenges when it comes to implementation. I would…
In a question here at Experts Exchange (https://www.experts-exchange.com/questions/29062564/Adobe-acrobat-reader-DC.html), a member asked how to create a signature in Adobe Acrobat Reader DC (the free Reader product, not the paid, full Acrobat produ…
Screencast - Getting to Know the Pipeline
Suggested Courses

872 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question