|
Nope. One set of anklebiters is enough for anybody.
|
|
|
|
|
More than enough, in my experience~!
___________________________________________
.\\axxx
(That's an 'M')
|
|
|
|
|
Great answer. 
Only caveat would be with #defines and #if/#else. Since C# DOES recognize those, the cpp preprocessor might be problematic if you used them for any reason (i.e. #if DEBUG blah)
|
|
|
|
|
Yes, but I have ways of dealing with them.
Actually, I only use it for # defines, it goes back to my PRO*C days.
|
|
|
|
|
|
Yes, but generally just constants like:
# define MAXNAMELEN 32
I kinda wish there were a different directive for macroes.
It would also be good if the pre-processor took a switch to indicate it should only process the # defines and not other directives.
|
|
|
|
|
Or maybe I misunderstood. My technique for having the C-preprocessor process only # defines goes back to my PRO*C days.
But, yes, I do (kinda/sorta) use macroes in my C# code... just to prove the point. But only when using CSC; I haven't bothered to try to use them with Visual Studio. Even though Microsoft gives good reasons for frowning on macroes in C#, I believe a bigger factor was integration with VS, and I don't fault them on that.
|
|
|
|
|
Thanks for your responses guys, and just to say that I have managed to adapt PIEBALDconsult's creative solution into something that will work in a straight-through build run with MSBuild rather than Csc. I can now run VS Projects and have MSBuild selectively pre-process files that have #includes in them, and process the others normally in one run.
The 'trick', if you like, was to set up a custom Task that does the preprocessing if it finds a file with a given extension (and I've used PIEBALD's .csi). All the code is actually written in .cs files, but the build is looking for .csi's in specified cases, and the custom Task is doing the pre-processing and generating these 'pre-build'. All I have to do is link my Task into the project in the 'BeforeBuild' targets:
<Project ... >
...
<Target Name="BeforeBuild">
<PreProcessor
Sender="$(RootNamespace).$(AssemblyName)"
Sources="@(Compile)"
/>
</Target>
<UsingTask Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' "
TaskName="PreProcessor"
AssemblyFile="bin\Debug\Com.Cinsault.PreProcessor.dll"
/>
<UsingTask Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' "
TaskName="PreProcessor"
AssemblyFile="bin\Release\Com.Cinsault.PreProcessor.dll"
/>
</Target>
</Project>
and the pre-processing of the headers is done before the build starts. I suppose there are just a couple of issues though. The most inconvenient is that, as the coding is done in the .cs file, but the build is working off the intermediate file, then any errors or warnings in VS are pointing to the wrong one, and the line numbers will be out too because of the included header code. The other is that, on the first run, MSBuild must find something for the files that it expects, even if these are empty, otherwise - even though the pre-build Task gets to do it's stuff first - MSBuild is looking ahead and saying "I got nothing to work with here!"
Could be useful though, so thanks again.
BS
|
|
|
|
|
You can pass your C# code through the "C-preprocessor", there's nothing stopping you, but I wouldn't recommend that in this case.
Have you considered class Project : My.Namespace.XMLProjectNode {} ?
That would point up that perhaps your classes like ...Node should perhaps be abstract.
|
|
|
|
|
Hi,
I'm developing a dll with C#.
The dll opens port, transmits and receives information. It works with RS-232, USB and Ethernet communications.
In this moment, I'm trying with USB communication and I have a problem.
C# shows me an error:
The name 'InvokeRequired' doesn't exist in the actual context.
The name 'Invoke' doesn't exist in the actual context.
I read that dll's don't recognize Invoke and InvokeRequired, and I have this code:
private void usb_OnSpecifiedDeviceRemoved(object sender, EventArgs e)
{
if (InvokeRequired)
{
Invoke(new EventHandler(usb_OnSpecifiedDeviceRemoved), new object[] { sender, e });
}
else
{
}
}
Is there another code to replace the above?
Thanks.
|
|
|
|
|
No offense, but your code looks.. strange
It looks like you're trying to re-fire the event on the UI thread if "required".
You could just invoke "whatever is in the else clause" but that boils down to the same thing.
Except that Invoke doesn't exist, apparently. Does intellisense show Invoke and/or InvokeRequired? Is this code inside a form? (if not, why are you using it?)
If you're trying to re-fire the event on "a thread other than the UI thread" you could give it a queue of delegates that it periodically checks (and calls them if there are any), I know of no other way to "inject" a call into a thread nicely but if there is someone else will post here 
|
|
|
|
|
|
How can I make software lock ( or Activation Code) for web applications ?
Your prompt reply will be appreciated …
regards
|
|
|
|
|
I assume you would have to have a database of users and an encryption algorithm for generating valid activation codes. Then track activations depending on the user.
Regards,
Thomas Stockwell
Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Visit my Blog
|
|
|
|
|
Please do not cross post.
Christian Graus
Driven to the arms of OSX by Vista.
|
|
|
|
|
|
|
PIEBALDconsult wrote: .IsAlive?
this.Thread.IsDead(); 
|
|
|
|
|
Alas, I hardly got to know it. 
|
|
|
|
|
When I am using switch statements in C# what is the most efficient type of switch variable to use?
Normally I only have less than 10 cases which makes an Int32 seem rather overkill but am I correct in assuming that as the machine is running 32 bits that may be more efficient than trimming the switch variable down to 16 or even 8 bits which may cause more code steps?
Cheers, Bruce 
|
|
|
|
|
Probably, test it and let us know.
|
|
|
|
|
Hi Bruce,
in general integer operations are fastest for the native word size, meaning 8-bit or 16-bit operations are not faster than 32-bit operations on modern CPUs.
This tells us byte and short mainly exist to support compatibility with existing data structures, files, etc; and of course to economize on memory when using large amounts of them as in arrays.
BTW: This may not be very easy to test, since (1) programming languages use the native size for literal values anyway, and (2) often the compiler will use int operations although byte or short where coded when those ints are equivalent to what you actually coded.
Luc Pattyn [Forum Guidelines] [My Articles]
- before you ask a question here, search CodeProject, then Google
- the quality and detail of your question reflects on the effectiveness of the help you are likely to get
- use the code block button (PRE tags) to preserve formatting when showing multi-line code snippets
modified on Sunday, June 12, 2011 8:35 AM
|
|
|
|
|
Luc Pattyn wrote: often the compiler will use int operations although byte or short where coded
That's what I would expect; a bunch of up-casting to int.
|
|
|
|
|
Luc Pattyn wrote: economize on memory
Interesting point - I've never delved that deep into the CPU architecture. Are things always word aligned or byte aligned, or is it variable? If it's word aligned then there would be no advantage at all to using anything less than the native size.
DaveBTW, in software, hope and pray is not a viable strategy. (Luc Pattyn)Visual Basic is not used by normal people so we're not covering it here. (Uncyclopedia)
|
|
|
|
|
structs can be laid exactly as required. Each element of an array of bytes comes immediately after the previous. Etc.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
