Quote:
Originally Posted by agraham
Not a good idea I think. You can't use line 2 anyway. That is reserved for a "//unsafe" line to allow for compiling code that needs to be flagged unsafe and/or for one or more further lines can follow defining "//ref: xxxx" references to other libraries in the Libraries folder that need to be referenced. Also I was considering suggesting to Erel a further option for a "//inc: xxxx" flag to allow multiple cs files to be merged.
|
This I didn't know..need to come up with another way to get the description or simply drop it...
Quote:
|
As long as the single cs file compiles OK it is likely that the name of it is not the same as the name of the dll. MyLibrary.dll must have MyLibrary.cs in the Libraries folder to merge. The lack of a "//version: x" line doesn't matter.
|
I did not compile, I just took both cs files and "merged" them using notepad...then copied them to the libs folder...
I'll get a better look at it in a day or too...
I'm having my last PC minutes, as i will be withou PC for a day or two...while moving back to my....other house...
EDIT:
its been a good coding day... got this bit working, and am now able to merge my former 2 cs file dll into a single cs file and merge the dll in the exe during compilation...
__________________
Paulo Gomes - Porto, Portugal - Living/Working in France
Mobile Device: Samsung Galaxy S, Android 2.3.4 CUstom ROM
Laptop: Toshiba NB100-130 (running on Win7Ultimate)

My Posts helped you? Consider Buying me a Porto Glass!