As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
Can you suggest me a possible way to get started with CEP in C# ?
By what I mean when I say, get started:
A good book talking about CEP and C#
A library which deals event clouds
Some sample codes using the library
Some good quality codes in general to get a possible feel of the problems
Good blogs
Anything else you might feel necessary to add for someone getting started in CEP and C# will be helpful.
Thanks
Soham
There is no such book. Yet. There is an upcoming book in the next couple of weeks from Manning called Event Processing in Action, it is a 'must read'.
For C#, the obvious choice is StreamInsight from Microsoft. There's a collection of useful links here: StreamInsight Info
Apart from that, there's StreamBase, Oracle CEP Server, ruleCore CEP Server and the open source Esper. Most (not Esper) vendors take a language neutral approach so you would not need to care in which language the CEP product uses when sending events into it.
From your question it sounds as you would like to do CEP programming. Many tools have a higher form of abstraction. For example StreamBase have a nice GUI where you select different functions from a palette of icons and then connect them in order to make it do what you like.
The ruleCore CEP Server has a high level declarative language where you specify the CEP rules using XML. Both these approaches are in my view not programming.
Esper and StreamInsight are good examples of putting CEP functionality in there that can be reached from your normal programming language. So if programming is what you like to do, StreamInsight is a good candidate.
No, StreamInsight does not require learning XML. But even if it would, basic XML is very easy to learn...
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I'm starting a new project to handle info from some text files, a kind of sorting module so I'd like to give it a try using LINQ but looking for a book I realized that there are more c# books than vb, so I wonder if c# have better support or if it is more suitable than vb.
You think there is some advance on use c# or vb.
thanks.
Better question: Why are there more books for C# than VB.
More developers use it. Simple as that.
http://www.telerikwatch.com/2008/04/survey-says-c-more-popular-than-vb.html
Interesting links on Adoption of C# and VB: http://en.wikipedia.org/wiki/Comparison_of_C_Sharp_and_Visual_Basic_.NET#Adoption_and_community_support
Most importantly for this question: Stephen Wiley, marketing product manager at Apress has reported "C# titles outsell VB.NET title books handily, by somewhere between a 2–1 and 3–1 margin."
So if you are looking for community support, I would say C# is the way to go, though MS does support both equally.
Generally the languages are the same, but there is a big difference in the perception of the languages and the types of examples and books available. In many cases you'll find more advanced examples in C# and advanced books in C# (not all, but many). You'll also often see people refer to C# as a superior language, not for any real technical reason but really from a matter of perception.
In my personal experience, you'll also see a difference in pay scales for C# developers vs VB.NET developers.
If you're just starting out, then I would recommend C# and not VB.NET. Again, not for any true technical difference, but because of the perception and available learning materials.
At the end of the day, its all syntax - especially in .net, because they compile down to be used by the same runtime engine. Perception is a big part, because c# looks more 'authentic', but its more based on perception. Also, c# syntax is very much like java, which is a language highly reverred amongst programmers. So, the natural progression says that more people will probably use c# than vb, and vb.net's grandfather (vb6) wasn't a good language...hence there are more resources for it..
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 12 years ago.
i need to write an web crawler and i need need which is best language for performance like memory and performance ..
Edit: Original title was "which language is optimized for speed and perfomance c++ or C#"
i need to write an web crawler
In that case, the internet traffic is probably your bottleneck, so the language does not matter at all.
I'd say that, if you know what you're doing, C++ is more likely to be efficient than C#.
On the flip side, C# is probably easier to work with and to optimize your app in.
So, since you have to ask, I recommend C# in your case. ;)
C++ virtually always offers the best performance of any language that supports modern programming techniques like generic programming and OOP. You pay a price for this though - it's substantially harder to use than C#.
Of course C++. You can manage every byte of memory there, while C# is Managed Code, where you tell the framework what you want to do and the framework does the things you usually do in C++. But if that's the main motive - don't stop at C++ and get right to machine code, Assembly.
A Google search would give you an instant answer - C++ is (generally) a better performing language.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 12 years ago.
I've been learning programming for some months now, mainly with java and C#. They seem so similar from my limited knowledge, so I'm trying to grasp an understanding of the practical differences. Could seasoned programmers please enlighten me as to which programming language is more suited for which kinds of jobs?
In what situation would you say "To create this kind of software, java is more suitable than C#" or "To create this kind of sofware, C# is more suitable than java"?
Java was originally designed to be the portable solution. If you need something to run on multiple operating systems you would probably want to go with Java.
From my experience in the financial world, the trend I see most commonly is Java being used on the backend (typically Linux servers) and C# (WPF) being used on the front end. I think this trend is here to stay until either Mono becomes widely accepted or Microsoft figures out a way to make their Server OS's free :)
I'm not saying Java is more suited for back end than C# (although I do think WPF has the edge over anything Java has for front end development) all I'm saying is that this is a very common trend in many financial/trading systems.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
Most C# developers developers, like me have a good solid grasp on the .net framework and the C# language. But I've yet to come across a book that can take a very good c# developer to the next level of C# mastery.
I am looking for a book that can help me make that transition. Dealing with issues like theory on having more robust C# code when connecting to external systems etc. Error logging techniques, and generally better memory usage, and re factoring.
Anyone know of a good book, that's worth the read?
Jon Skeet's "C# in Depth" is pretty good: http://www.amazon.com/C-Depth-Jon-Skeet/dp/1933988363/ref=sr_1_1?ie=UTF8&s=books&qid=1259183768&sr=8-1
Effective C# and More Effective C# by Bill Wagner come highly recommended
If you're a very good C# dev, you should perhaps look beyond a certain language and technology and try: Domain Driven Design. It's a great book and promotes ideas that help writing great software.
The best book I have found for C# internals is CLR via C# by Jeffrey Richter.
Not a C# book per se, but Design Patterns (Gamma et al) might be a good introduction to more abstract, architectural concepts.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I'm starting my 2nd class in C# programming through Kaplan online school. I have some limited interaction with the professor and the class online, but nothing like in an actual school. I'm about to go through "Modern Software Development Using C#.NET" by Richard Wiener. It seems the book as a extremely heavy focus on UML (which I don't even really know what that is right now!)
You experinced Csharpers.... any tips to keep in mind as I go through this to keep in perspective how the modern software engineer works outside the classroom?
Any perspectives to share as I start understanding UML and intermediate C# programming?
Some companies will use UML everywhere. Some use it nowhere. I'm not a big fan myself - I prefer ad-hoc diagrams and plenty of other communication (notes on the diagram, actual talking etc).
The good thing about an ad-hoc approach is that you can leave it as vague as you like or make it really detailed. The bad thing about it is you can't generate any code from it - but I've never really liked generating code from UML. (Others swear by it, mind.)
You certainly don't need to know UML to learn C#.
UML would come very close to the end of the list of things that gave me insight into the complex world of programming. I find it very distracting when trying to design something, and too time consuming for real system descriptions. I have always thought it is important and tried to start my project with UML diagram, but it wasn't ever worth it.
The bigger the projects you are working in the more you need a language to speak with, known by all members of the project team - a common language like UML! But you need not to start learning C# with UML.