Is it Acceptable for Referenced DLLs to reside in the project's \bin\Debug folder?
Amos Moses was a wimp! "Rassling" alligators is nothing compared to this CE / CF Gordian Knotesque mass of spaghetti I'm dealing with.
In my latest gyrations to try to somehow coax this big ball of mud to at least compile and run, I notice that some of the referenced DLLs live in the project's own \bin\Debug folder.
Is that safe, and sound? It seems rather tail-chasey or circular-referencey to me. It appears to work, but...would I be better off moving those DLLs elsewhere?
UPDATE
To be clear, here is what is in \bin\Debug:
...in \bin\Release:
...and how the OpenNETCF* DLLs are referenced:
It appears to work, but...would I be better off moving those DLLs elsewhere?
In general, I would not recommend having that be the referenced location. It is common to have the referenced assemblies copied to that folder, but they should live elsewhere (and have their HintPath in the C# project file referencing the other location).
- Waitpid equivalent with timeout?
- How do I get bit-by-bit data from an integer value in C?
- Decent ways to handle malloc failure?
- POSIX way to do O_DIRECT?
- Why do I not get a MessageBox popup when calling MessageBoxA
- C Compiler differences for iOS and Android development
- different initializ and sign pointer value in global and function
- Hi-Tech C Compiler: #define: "taking the address of this object is illegal"
- Should we disable compiler optimization until the program is bug free?
- Is it possible to convert C to asm without link libc on Linux?
- Explanation of Permission Bits
- Why are bitfields not tightly packed in a struct?
- Why is variable sized object initialization not allowed using const
- C not operator applied to int?
- When to use restrict and when not to
- Why the first node of a linked list is declared as a pointer?
- Problem with not working gdk_test_simulate_button in GTK3
- Configuring the STM32F407VET6 ADC using CMSIS
- Allow double floating point comparisons with Unity unit testing framework from Throw The Switch
- CMake imported library behaviour
- libssh2 public key authentication only requiring passphrase if key request is accepted
- Are arrays treated as static data structures by gcc compiler or as dynamic?
- Is there a 128 bit integer in gcc?
- Loading c library from c# with pinvoke on dotnet core
- Why does my compiler not accept fork(), despite my inclusion of <unistd.h>?
- C/C++ warn or prohibit literal string concatenation
- Fastest way to write & compile a C/C++ program in Windows
- How to pass a 2D dynamically allocated array to a function?
- Behavior of scanset
- How to create an ada lib.a and link to C