|
JayKhatri wrote: My question is should I continue using datatable instead of arrays as it gives me great extension and flexibility. Is it a gud idea.
Yes/no.
As stated, it does offer you some advantages over arrays. If it speeds up the development-proces without impacting the performance too much, go for it. It does cost a bit more resources, but most PC's have (often more than) a GB of memory.
I'd recommend using a Generic.List though, as they combine the best of both worlds 
I are Troll 
|
|
|
|
|
Then I will study Generic.list first. Thanks for your reply.
|
|
|
|
|
Hi,
I am using Dim str as string frequently in my windows application mostly to fill any dataset to query anything and more.
basically how I use this is as follows:
Dim dSetTemp As New DataSet
Dim str As String
str = "select trans_vchr.trans_vchr_id, trans_vchr.session_cfee_id, blah blah...."
dSetTemp = clscmn.Fill_DS(str) --> fill_ds is a function created to increase the productivity.
Here if I like I can easily do the same like this
dSetTemp = clscmn.Fill_DS("select trans_vchr.trans_vchr_id, trans_vchr.session_cfee_id, blah blah....")
Here my question is whether I use str variable or not, actually I use the variable as it make my debugging so easy I just copy the string and paste in sql to test the query. Here that gives me productivity while debugging but if it is at the cost of performance. I would compromise with debugging facility or If it is negligible, it can be left.
Can you suggest what will be best for me. I like to save bytes to be loaded in memory and like to have best performance.
Thanks in Advance.
Jay Khatri
|
|
|
|
|
IMO the cost difference is very small and irrelevant; the debugging comfort is a perfect reason for using the string variable.
|
|
|
|
|
thanks for such a quicky answer.
|
|
|
|
|
Yeah, I agree with Luc, this seems like such a small impact that the benefits of being able to 'see' the string in the debugger might outweigh the efficiency of the hard coded string...
But if you ever have questions like this again you can also do a few things...
1) Code it both ways and open the executables up in reflector to see the IL. That sometimes shows you that no matter how you 'code' it, the compiler may just be optimizing it out for you.
2) Code it both ways and throw it in a huge loop then run it a few thousand times to get some performance numbers. See how it uses memory. See how the GC acts, etc...
|
|
|
|
|
nice one ray and impressive too. Thanks alot for your anticipation. I have more queries which arise time by time. Hope I will get this kind of reply then.
Best Regards
Jay Khatri
|
|
|
|
|
Ray is correct, but he left out one little detail. If you run the code compiled under Debug build, optimizations are turned off. This can make the code run a bit differently (and slower) in Debug then it would in Release. So if you want to test this, make sure you compile a Release build.
|
|
|
|
|
Great!!! that make a big difference.
Thanks for the addition.
Jay Khatri
|
|
|
|
|
Yes, I agree, and it can change the way the IL is constructed also. Thanks for bringing that up.
|
|
|
|
|
Not a problem. It's something that I was reminded of about a week ago. 
|
|
|
|
|
I generally go with whatever is more readable (if its a long string and i use it inline then it pushes the rest of the method off the screen) and easiest to debug.
One thing to consider though, if you have a string that is potentially being declared inline then that string is a constant, why not make it a constant?
As part of my 'final tidyup' i generally go through my code looking for " characters and numbers, if i find any i ask myself why they aren't constant, 9 times out of 10 they should be 
|
|
|
|
|
Hi All,
I am designing brand new application using the following technologies.
C#
ASP.Net
AJAX
SQL SERVER 2005
Visual Studio 2008.
Approach's
3-Tier architecture
UI+BL+DL classical way.
UI+BL+DL with Application blocks.
N-Tier architecture
UI+BL+Linq to SQL
UI+BL+WCF+database
Can you please help me which approach will give best performance.
Thanks & Regards
Rao
|
|
|
|
|
And don't cross post in multiple forums.
|
|
|
|
|
hi everyone..
I want a tool to plot real time graph for .net platform.The data which has to be plotted is continuously coming in some time interval.Is there any tool available?
Also Performance issue is there.Performance also matters when I am using the tool.
Thanks in adv...
|
|
|
|
|
jainiraj wrote: I want a tool to plot real time graph for .net platform
.NET isn't a "realtime" platform, nor is Windows.
jainiraj wrote: The data which has to be plotted is continuously coming in some time interval.Is there any tool available?
Write an application that handles the communication and stuffs the data in a queue. Have another one draw some nice graph using that data. There should be some articles on charts. Bars or pies?
jainiraj wrote: Also Performance issue is there.Performance also matters when I am using the tool.
Simple; don't use VB6
As a reminder; cross-posting isn't a nice thing to do.
I are Troll
|
|
|
|
|
I was told I should probably ask this here, even though it relates to MFC, it is probably more a design question. So,
At my workplace we have a number of programs (sub systems) which make up our software. Some of these programs need functionality from other programs and I'm trying to find a good way to perhaps modularize each program so that common code/resources can be used "globally". The current example forcing me to find a solution is the need to launch a dialog from our Accounting package from another sub system. The big problem is that this is quite a large dialog and depends a lot on things from the Accountings MainFrame.
I was thinking that for each sub system I could create a DLL which contained common dialogs, etc that could be used by other programs. The problem I face is that a lot of the dialogs have dependencies on their parent programs MainFrame and I'm not sure how to get around it. I guess one solution might be to take everything out of the MainFrame and put it into its own class which can then be passed to the DLL.. but I don't even know if that would work as I still need to Initialise this new class the same way it would be done in the parents program, but now in the other sub system.. though in saying that the DLL should probably be responsible for setting itself up.
Your thoughts?
Cheers
|
|
|
|
|
Aaronov wrote: I was thinking that for each sub system I could create a DLL which contained common dialogs, etc that could be used by other programs. The problem I face is that a lot of the dialogs have dependencies on their parent programs MainFrame and I'm not sure how to get around it.
That will depend on the type of dependency. If it's an enum that get's shared, move it to another library that both the DialogDll and the ParentProgram can access. That could also be done for customized buttons and UserControls - if those have been designed with a separation of UI/data.
It it's data that the dialog depends on, I'd suggest using some kind of IPC with the ParentProgram, or calling a webservice that interacts with the ParentProgram's datastore.
Aaronov wrote: though in saying that the DLL should probably be responsible for setting itself up.
Can I translate that to "the class inside the assembly is responsible for constructing itself?"
I are Troll
|
|
|
|
|
Yep, that translation is correct. The code that is moved from MainFrame into a class in the DLL is responsible for setting itself up. The dependencies are mostly just basic variables, enums, etc so I think it will work by moving them into a DLL.
What's an IPC?
|
|
|
|
|
Aaronov wrote: What's an IPC?
Inter-Process Communication
Pipes, mailslots, memory-mapped files.....
|
|
|
|
|
Hi everyone,
I have been developing C# applications for about a year now and I am starting to grasp the more advanced topics. The problem is, I know enough about the C# language to write code for ADO.NET and other technologies, but not skilled enough to write code adhering to design patterns and encapsulation (i.e all my code is written in codebehind in my form class).
I am now stuck in a bind because I don't want to write code in code behind, since I have been reading it is hard to maintain, etc, etc but I am not yet good enough to properly setup inheritence and good design in my code base!
Is it ok to develop a large application all in code behind and then try to refactor it out later?
I am just completely stuck!
Any help appreciated
Dave
|
|
|
|
|
DavidKiryazi wrote: Is it ok to develop a large application all in code behind and then try to refactor it out later?
Absolutely not.
if you to do so,you will find the workload is far beyond your imagination.
did you read any article about "Object-oriented design patterns"?
|
|
|
|
|
thanks for response Alegria.
I haven't read any books about design patterns. I have mentioned it to a couple of work colleagues but they insist that the best way to learn is just to write code. I disagree because I guess my opinion is that if you learn to write bad code, then it will be harder to change your ways later on.
I guess I might need to read a good book on object oriented design and design patterns. I know the GOF is a must, but apart from that is there any you can recommend to get me up and going? Basically I need something that teaches me OOD that does not use the simple examples like Cars.
I am also considering the purchase of Code Complete 2 and I have stated reading "The Pragmatic Programmer"
Dave
|
|
|
|
|
Code Complete is a great book. I own it and I make it a point to re-read through it every year just as a reminder/refresher. That and 'Software Requirements' by Karl Wiegers is great too.
GOF is important from a high level conceptual point, but in reality I think you will find that thinking in OOP is clearly more important than learning a bunch of patterns. Not that they don;t give some great advice, but I personally think that learning to think in layers is more important that focusing on learning a set of specific patterns.
Don't get hung up so much on the simple examples that most book use as much as making sure you get the higher level ideas behind them. Remember that authors have to not only write so the reader can understand a complicated concept but often times the 'editors' at the book companies can have a huge impact on the content of a book and cause it to be dumbed down a bit too much. You want to read some great stuff on OOD grab yourself a membership to ACM (or IEEE if you happen to be independently wealthy) and read some of the papers submitted there. Some good reads.
If you really want to get used to thinking in a detached manner (IE: code implementation separate from UI and data layers, take a look at doing some work in SilverLight. It FORCES you to NOT put code in your UI layer at all, simply because you really can't. It makes you think in layers and that is a good thing that you can end up leveraging even in the regular application world.
|
|
|
|
|
The Pragmatic Programmer is a gr8 book. I have a paperback and like to read it often.
It gives you discipline in writing code.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
