|
You can use the DateTime.TryParse()[^] method to convert your strings, and then use the other methods of the DateTime class to perform your calculations.
One of these days I'm going to think of a really clever signature.
|
|
|
|
|
A "Certificate Revocation List"?
It seems that you already have an answer on your question in Q&A. Was it not satisfactory?
|
|
|
|
|
I am finishing up my program, and I built just like an typical amateur does, only one process works at a time. I need to start multi-threading, but because of the considerable amount of repeditive type of calculations non graphic I was wondering how I might proceed.
I need to run 8000 sets of data through the same algorithms which may be up to 1000 every few minutes. Furthermore how does this fit in with using a multiple processors with multicore cores and will it speed it up, if it will do I need to set the threading up accordingly.
Right now I have an older machine with a dual core and it processes about 10 data sets a second, will I be able to set up the program where I can use dual processors with multi-cores and speed up this process (other than the processor speed).
Or do I need to use a blade server and split up the program to process more data, if so do I thread it differently also.
Any help would be greatly appreciated.
Thanks in advance.
Michael
|
|
|
|
|
The benefit you get depends on your datasets and how they need to be processed. You have a couple of options for dividing the work up:
1) Each thread will handle its own dataset, processing each, by itself, from start to finish. The benefit you get is if you have more than one dataset being worked on at a time.
2) If your dataset can be worked on if you partition a dataset into smaller chunks, each thread can work on a small chunk of the data. Say your dataset has 100 items in it and each can be processed individually with no dependancies on the other items in the set. Partitioning the dataset means breaking the 100 items into groups of, say, 25 each. Then 4 threads could work on the same dataset, each processing 25 items seperate from the others.
In both cases, you're best benefit is usually obtained when the number of worker threads you create matches the number of cores in the CPU. So, if you have an Intel proc with 4 cores and 4 hyperthreads, you'll see 8 logical cores, so you can get away with 8 threads.
You can also look into the Task Parallel Library (pre .NET 4.0) to simplify this process greatly. If using .NET 4.0 or 4.5, the TPL is integrated into the .NET Framework. You don't have to install a seperate library to use it.
See the System.Threading.Tasks namespace documentation.
|
|
|
|
|
I would difinely go with option 1 below because all data sets will not be processed to completion.
You said for every core you would have a separate thread, does this mean whether I use a single server with 2 processors and multiple cores or blade server with multiple computers it is only the number of cores that is important.
modified 6-Dec-12 0:46am.
|
|
|
|
|
You cannot start a thread on a seperate computer. If you want to use blade servers, each will have to run a seperate copy of your app and you'll have to come up with some way to spread the number of datasets over the set of servers and communicate with each.
|
|
|
|
|
i want to develop 4*6,6*10 inches photo format in my application plz help
|
|
|
|
|
You're going to have to go into quite a bit more detail than that if you want any real help.
|
|
|
|
|
I want to develop:
A telepathic application that can read a users mind and instantly respond.
A time travel application that can get information from the future.
A direct mind - computer link
Ok so its a quiet afternoon and I'm a little bored! Give us something to work with here, your question makes about as much sense as my answer!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Through me on that mailing list for when those are done but you should add one more app to the list: A telepathic application that can read a clients mind and translate that into coherent specification documents.
Oh yea and a Do Work button would be fantastic addition as well.
Don't comment your code - it was hard to write, it should be hard to read!
|
|
|
|
|
The Do Work button is a done deal - takes up 98% of the screen, is lurid red and has the text Press Me, I didn't want to scare the client with the thought of actually working. It was the last time that particular idiot ask for I want just one button, not all the complex sh*t.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I have a question about converting a C# 2010 application that is currently run as an executable to be run as a DLL instead. I do not know what parts of the entire solution file should be part of the dll file and what parts (if any) should remain as an executable.
I was briefly advised by a contract shop that when the current application calls a web service, that portion should become the dll. I was also told by the contract shop that the chelper.cs code (that calls the web service) should be part of the dll.
This same contract shop also said I could write separate dlls for each 'type' of method that is called. If I did that, I would use portions of code from each project file.
So basically I have part of one project file out of 4 project files that should be included in the dll file?
Here is a description of the current project files:
1. one project file has various routines that are tied with the web service.
2. Another project file is a handshaker to verify security.
3. There is the 'driver' project file.
4. There is a 'sample' code project file that was written by the contract shop that supports the web service.
Can you tell me how you would decide to setup the application I listed above as dll file(s)? How would you
change the code that I just listed above? How would you setup the code tio convert it (use it) as a dll file?
|
|
|
|
|
Based on your requirements, you will not convert your entire project into a dll.
Try to group out all the business / data layer components and moved them into the service layer.
The executable file will still need to call the service.
|
|
|
|
|
I wouldn't make any changes just because someone else says I should. And I'm not impressed with what you've said they said.
Does the system work?
There's nothing magical about DLLs and they can't do anything an executable can't do.
At the extreme, only the main method needs to be in an EXE and everything else can be in a DLL -- but would it make sense for you to do it that way just to satisfy someone who won't have to live with the code?
As mentioned, think in terms of layers; put a minimum of code in the top-most layer -- that could be the EXE and everything else can be in one or more DLLs if that makes sense to you.
Also: how likely are you to need to refer to the DLL from another app? If not, then why bother?
|
|
|
|
|
I wanted to mention that the program I talking about is executed from 2 other programs. Thus does it make sense to make part of this called program a dll?
|
|
|
|
|
|
I agree with Piebald, restructuring for it's own sake is a waste of time, if you don't have a reason to make the change then don't bother.
Having said that I always structure an application, I imagine any developer quickly comes to this decision, I would keep the UI elements in the exe, the business logic in another and the data access in a third but this is just for my convenience and to make support easier.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Is this the same contract shop that gave you a console app to control the web service? If it is, any advice from them should be ignored as they are clueless morons who should be kept away from electronic equipment.
|
|
|
|
|
how can I be a professional in C#.Net framework ?
what should I do?
|
|
|
|
|
Study, study, study and practice, practice, practice.
One of these days I'm going to think of a really clever signature.
|
|
|
|
|
"Any sort of work in VB6 is bound to provide several WTF moments." - Christian Graus
|
|
|
|
|
As Richard said, practice and study. No one can become a professional at something without practicing and studying. You might want to read up on .NET Book Zero[^] 
"Any sort of work in VB6 is bound to provide several WTF moments." - Christian Graus
|
|
|
|
|
Paul Conrad wrote: .NET Book Zero
The first book I read when trying to understand C# and .NET.
One of these days I'm going to think of a really clever signature.
|
|
|
|
|
Hello guys,
I am doing a C# application + SQL Server DB to manage employees, contracts, rate of work, contract durations, hourly rates... and do some funny calculations with that.
Basically, I need to store some values with the format "0000,0000" in my DB
I have actually build my app interface with winforms and i didn't have any problem to insert, select, update to my SQL Server DB, until I started to play with the numeric/double/float values 
- I have set my table with all columns where i require these "000,0000" values to decimal
- In my forms, i haven't specified any specific properties to my textboxes,
- To insert I use a method for which i defined decimal arguments
public void createNewContract(int employeeId, string agency, string role, string contractType, string startDate,
string endDate, string lineManager, string reportTo, string costCenter, string functionEng, string atrNo, string atrDate, string prNo, string prDate,
string poNo, string poDate, string comments, decimal duration, decimal workRatePercent, string currency, decimal hourlyRate, decimal value)
- To capture my textbox values and send them through my method 'createNewContrat', I have tried
Convert.ToDecimal(this.txtDuration.Text)
and plenty other things that seemed good to me, but i don't manage to understand the mechanic and i'm certainly not using the most pratical/clever solution... 
What would you recommend?
Thank you for your help
Brice
|
|
|
|
|
I prefer a NumericUpDown for numeric values. TextBoxes are for text.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
