|
I have to deal with barcodes a lot, just not from a programming stand point. We exclusively use 3of9 as the format. With 3of9 you must have a leading * and a trailing *. Those are the starting and ending points for the software to read the barcode.
I am sure other formats are different, just research your format.
|
|
|
|
|
|
Depending on the ink, paper, and barcode size, the ink can spread after printing, making the barcode unreadable. This phenomenon is called "dot gain".
The way to correct for it is "bar shaving"; you remove column(s) of pixels at one or both edges of the bars to make them narrower. For 2D and GS1 barcodes, which have both vertical and horizontal dot gain, you can do bar shaving in two dimensions. (This is also called "erosion"; an operator from mathematical morphology). This is the mathematical inverse of dot gain.
|
|
|
|
|
hi
i want to make a setup of my c# project that i create on visual studio 2010 and use access database (for some reasons), but i don't know how i create to run on a server.
thnx
modified 28-May-13 10:51am.
|
|
|
|
|
There is no difference between creating a setup that runs on a workstation or on server. It's Windows in either case and everything still works the same way between the two editions as far as a Setup is concerned.
|
|
|
|
|
I do not think that that's a problem of the setup: You'll need a Windows Service instead of a Windows (GUI) / or Console application. That means some bigger changes to your project.
|
|
|
|
|
what can i do for this problem so that i manage to run my program
through the server ??
|
|
|
|
|
You're going to have to define exactly what you mean by "run the program through the server".
Are you placing the executable and all related code in a share on the server and client machines will launch it from there? Are you saying that you want the client machines to remote desktop into the server and run your app on the server? ...??
|
|
|
|
|
i want to have my database in a server and my program in clients so the clients can get correct information from the database any time they want.
Also i want users have the ability every time they make changes in some records these records have to be
locked for others users until this user have finished...
|
|
|
|
|
OK, so you can either create two seperate installers, one for the database and one for the clients, or you can combine the two and the first client to install would go through the process to install the database on whatever SQL server the user specifies.
You REALLY have to be careful with record locking. It's just about never a good idea. The primary question is what happens if a client locks a record and then the client machine hangs?? How do you recover from a locked record that shouldn't be locked any more??
Concurrency issues are not easy to solve and you have to do research into what you're options are and how they affect your business process code.
|
|
|
|
|
the setup process for the server it is the same with the setup process on laptop ?
or i have to follow different way to make the setup process for server?
|
|
|
|
|
What did i say? IT'S NO DIFFERENT. Windows Server is still frickin' Windiws! Everything works the scant same way.
|
|
|
|
|
|
I have a C# 2008/2010 application that is currently accessed as a dll file and I would like to change the application so that the dll is accessed though as a reference. The code that calls the dll is a process and the code looks like the following:
Process theProcess = new Process();
theProcess.StartInfo = new ProcessStartInfo("filename.ext");
theProcess.StartInfo.Arguments = "args here"
theProcess.WaitForExit();
theProcess.Start();
The problem is the dll is currently placed in various locations like unit test area, client acceptance testing, system testing, and then into production by the 5 applications that call it. The application currently obtains the various locations based upon values in the app.config file. If I add this dll has a reference to the programs that call it, how will I tell those calling programs where to obtain the 'correct' directory location? Would I use the app.config file?
Can you show me code and/or explain to me how to solve this issue?
|
|
|
|
|
Usually, the .DLL referenced will be in the same folder as the .EXE calling it.
But, if that's not possible because of multiple applications refering to the same .DLL, you can put it in another location suiteable for the task, such as a folder under C:\Program Files\Common Files\companyName.
Read this[^] for more information on your options.
You could use a probing path in the app.config for all the applications, but all applications would have to be under the same folder under program files and the .DLL path would have to be under the base application path.
|
|
|
|
|
If I place the dll in the same directory path for all 5 programs to access, that would be a good idea!
Currently each program executes the dll by the value placed in the app.config file for each of the 5 applications. Would I be able to continue to use the same logic? If not,what would need to change?
|
|
|
|
|
sc steinhayse wrote: If I place the dll in the same directory path for all 5 programs to access, that
would be a good idea!
Since I have no idea where these apps are installed and what your business requirements are, I have no idea!
But, if your requirement is that every app has the exact same version of the .DLL, it would probably be a bad idea to have 5 copies of it running around.
sc steinhayse wrote: Currently each program executes the dll by the value placed in the app.config
file for each of the 5 applications. Would I be able to continue to use the same
logic? If not,what would need to change?
This means absolutely nothing. I have no idea what you mean by "executes the DLL by the value placed in app.config". What value?? What does it describe?
|
|
|
|
|
Here is an example of the code that I am referring to in my question:
strConsoleAppLocation = ConfigurationManager.AppSettings["dll_location"];
string Process_Arguments = null;
Process RPT_Process = new Process();
RPT_Process.StartInfo.FileName = strConsoleAppLocation;
Process_Arguments = " 7 " + strCUSTID + " 1";
RPT_Process.StartInfo.Arguments = Process_Arguments;
RPT_Process.Start();
RPT_Process.WaitForExit();
RPT_Process.Dispose();
|
|
|
|
|
I am sorry about the confusion in the terminology. Each of the 5 program calls an exe and passes parameters to the exe.
What I am suppose to do is not call an 'exe'. I am suppose to have call each 'exe' in a faster manner.
what would a faster manner be? callin a dll?
|
|
|
|
|
If you're talking about the length of time it takes to launch an external .EXE, then you have no choice but to move the code that's in the .EXE into the code that's launching it. This will, of course, require you to rework your code in all 5 apps. You could put the code you're using in the .EXE into a Class Library project, which compiles to a .DLL, and then you've got the code in one place which you can use in any other .EXE.
|
|
|
|
|
I have a question about your following statement, "You could put the code you're using in the .EXE into a Class Library project, which compiles to a .DLL, and then you've got the code in one place which you can use in any other .EXE."
If I do what you suggest above and place the code into a .DLL, that means the dll would not take parameters correct? If this is true, is there another way i can share the code between all the programs and pass the parameter values?
|
|
|
|
|
sc steinhayse wrote: If I do what you suggest above and place the code into a .DLL
DLL's don't take parameters, period. They are containers for classes and modules, which contain methods, which can take parameters.
You SERISOULY need to pickup a beginners book on C# and work through it.
|
|
|
|
|
|
Question seems confusing to me.
A dll is not an executable so you are not using Process to run it.
So what is the exact form that it exists in now?
What is the exact form that it will be?
And why do you think you need to access it dynamically? Although the answer to that might be explict by the answer to the previous two questions.
But that said you can't answer how to dynamically load anything until you first decide how it will be delivered into production.
|
|
|
|
|
I have a C# 2008/2010 application that is currently accessed as a dll file and I would like to change the application so that the dll is accessed though as a reference. The code that calls the dll is a process and the code looks like the following:
Process theProcess = new Process();
theProcess.StartInfo = new ProcessStartInfo("filename.ext");
theProcess.StartInfo.Arguments = "args here"
theProcess.WaitForExit();
theProcess.Start();
I want to be able to pass argument values to the dll when it becomes a reference in the 5 programs that call it.
My problem is that I do not know how to pass the parameter values when the code is accessed as a reference. Thus can you tell me how to pass argument values to the application when it is accessed as a reference. Is it something in the reference call? Can you show me code and/or tell me how to acoomplish my goal?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
