That's rather a long question for a forum like this. Files (which usually have extensions) are held in directories, which may themselves be held in directories. Directories are generally now referred to as folders. Think of it as a set of filing cabinets. Each cabinet has drawers and each drawer has sections, and within each section are individual documents. When you click on a file the shell knows what to do with it by looking up the extension name in a table. So a file with a .exe extension is sent to the program loader and starts running as an independent program. A file with the .doc extension causes the loading of a program that can process it (probably Microsoft Word), and so on.
I think that they are well documented and despite that, still poorly understood. Guess I'm not really understanding the question here.
There's examples on authentication, which is what most customers refer to as security. OTOH, you'd also want to limit the number of consecutive requests, prohibit malformed requests, and log everything that seems "out of the ordinary".
If the communication needs to be 2-way then I would suggest that each system (you seem to be describing 2 but there could be more) have its own private output file which is read by the other(s). Each system writes its 'output' info to the file which would be seen as 'input' to the other(s). This avoids problems with 2 or more programs trying to write to the same file.
I have created a nice desktop application and I have no time (or money) to port it to metro. The good thing is that windows marketplace is selling desktop application too. Do you know the procedure and the cost of money that is needed to publish such a desktop application to windows 8 marketplace?
Do you know the procedure and the cost of money that is needed to publish such a desktop application to windows 8 marketplace?
No idea on the cost, but the procedure is here[^]. There are two types of accounts that you can create, a "individual" and a "company" account. Docs say that only the company-account supports the old desktop.
Bastard Programmer from Hell
if you can't read my code, try converting it here[^]
Thank you both for the information. $99 is not such a problem since the it will reach thousand of users and it will repay the investment for good, the problem is that I don't own a company and I cannot create a company account.
If you are expecting to make a decent amount of money out of this, then creating a company is probably a good idea. If you can't, have you considered selling your app through the Intel AppUp Store[^]? That allows you to sell as an individual.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
Living in Greece it is a drawn back for creating a company
Do you think that intel AppUp will accept desktop application? This is interesting, I'll check it when I get back home.
Hello, CP. So I am working on this application here at work and the current piece involves inventory management. First, I will list the tools I use:
Visual Studio 2010 Ultimate
C#, .NET 4.0
Microsoft SQL Server 2008 Enterprise
LINQ To SQL
Now, what I have are various types of items which need to be tracked. They are referred to as "RPCs" (and they are all computer parts). I have been thinking on this for a while but I need to figure out the most efficient way (both from a development standpoint as well as from an end-user standpoint) to input data and store these items in the database.
What I have done so far, for the first three types of RPCs, is I have created a UserControl. On that control are the fields necessary for that particular RPC type. Each RPC has various attributes which are not shared among other types. For example, a Hard Drive has Marketed Size, Physical Size (2.5" or 3.5"), RPM while a CPU has Clock Speed, Cache Size, # of Cores. I think you get the idea.
Well, I started out with these three UserControls as well as three tables in the database, one for each type. However, the issue really becomes known when I say this: to start with, I have roughly 25 diferent RPC types.
So is there a way I can keep from creating 25 UserControls, one for each type? Or 25 tables in the database just for RPCs? I thought about creating a single table with the specs that each type does have in common (e.g. Manufacturer, Model) an storing the specs in a specific format (e.g. XML) in a column and having the application manipulate the specs data as necessary. However, the performance issue arises when I think about the fact that I must be able to search various RPC types by one or more specs. For example, the application needs to be capable of finding all 500GB/7200RPM hard drives. That wouldn't work so well when using XML for all of the specs would it?
Maybe I am going about this whole thing all wrong. But then again, maybe I am better off going with the numerous tables and user controls. If that's what it takes, I'll do it. I just started thinking about it early on and realized that maybe I am not being entirely efficient with it.
djj55: Nice but may have a permission problem
Pete O'Hanlon: He has my permission to run it.
Last Visit: 31-Dec-99 18:00 Last Update: 24-Aug-17 1:34