|
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.
|
|
|
|
|
Any particular reason your createNewContract takes on 22 parameters? That is an eye sore. Why not have a class that holds the parameters and pass an instance of the class object as a parameter to improve readability.
"Any sort of work in VB6 is bound to provide several WTF moments." - Christian Graus
|
|
|
|
|
Thank you Paul,
I think you are driving me on a direction I wasn't thinking of
How would you do this (on a sample section of code)?
In general, what are the advantages of your solution compared to what I'm doing? Reuse/visibility?
The concept is new to me
Thank you
|
|
|
|
|
Yes, my post was not really directed to your actual question but an off topic observation I made. How to do my suggestion is pretty straightforward. Just have a class with properties that are the parameters (this is where you could check for invalid parameters as well - unless you have checks done elsewhere), and you populate the properties with the respective values and just pass the object.
The advantage is clarity and readability, and it doesn't hurt to have all the values you are passing to be encapsulated in a wrapper class. Either the way you have done it, or my suggestion, both work.
Back to your original post, I would second PIEBald's suggestion if it works for you.
"Any sort of work in VB6 is bound to provide several WTF moments." - Christian Graus
|
|
|
|
|
Something perhaps along the lines of:
public class Contract
{
int employeeId;
string agency, role, contractType, startDate, endDate, lineManager, reportTo;
string costCenter, functionEng, atrNo, atrDate, prNo, prDate, poNo, poDate;
string comments;
decimal duration, workRatePercent;
string currency;
decimal hourlyRate, value;
public Contract()
{
}
public int EmployeeId
{
get
{
return employeeId;
}
set
{
employeeId = value;
}
}
public static void createNewContract()
{
}
}
Inside the properties for anything that works with decimals, you can take care of the conversion there. Again, this is just a slight off topic suggestion, and I do not know how much work it would be to put this into your application, but it's a kind thought
"Any sort of work in VB6 is bound to provide several WTF moments." - Christian Graus
|
|
|
|
|
It all really make sense to me now
I'm going to pursue this way
Thanks a lot!
|
|
|
|
|
You're very welcome. At first, it sounds like it is a bit of extra coding, but it is worth it in the long run!
"Any sort of work in VB6 is bound to provide several WTF moments." - Christian Graus
|
|
|
|