|
Hello Experts,
I would like to ask a few guidelines in making an internet cafe software, I am kinda confuse if where should I start first.
Do I need to start from the client part or the server part. I am planning to use vb.net and sql server/ms access for the database
since I have use it in my previous project. I have created a project using vb.net and sql server in my past project and I wanted to try higher steps by doing network software. Any suggestions to help are kindly appreciated.
Thanks in advance,
DAN
|
|
|
|
|
I would suggest you start by writing down your specifications and how he timer will be used. Then what should be client and server will likely be obvious.
CQ de W5ALT
Walt Fair, Jr., P. E.
Comport Computing
Specializing in Technical Engineering Software
|
|
|
|
|
In additional to Walt's advice, for technology I would certainly be using SQL Server. You could start with SQL Express (its free) and upgrade when necessary much easier than starting with Access. As for language, and without starting a religious debate, IMO C# would be more appropriate. I believe there are more and better code samples available for you to learn from. Also since most network applications were, or still are, written in C++, the code is of better quality and it would be easier to translate to C# rather than VB given the similarities in syntax and structure between C++ and C#.
I know the language. I've read a book. - _Madmatt
|
|
|
|
|
Hello experts,
Thanks for all the suggestion and helpfull reply. Although I am not that good in c++ since vb is the 1st language
were I can use database on it I will give a shot on c++/c#.
Thanks,
DAN
|
|
|
|
|
I'll agree with Mark and Walt, but add my two cents worth. If I understand your question, you want a timer on the connections to an Internet Cafe application. I assume you want to charge for access by the minute, or some finite time chunk. You'll need to create a connection pool from which users "check out" connections for a period of time. To my thinking, the proper place to implement the timer is on the server side, as each connection is established. When a user pays the fee, a connection is enabled and the timer started. When the timer completes, the server is notified of the connection associated with it, and the server should suspend the connection and ask for more money. If the user declines, or fails to respond (having packed up and walked away), the server then closes the connection and returns it to the pool.
As has been mentioned, with a project this (potentially) complex, you really need to develop a detailed specification first, even if just for your own use. You're going to get quickly overwhelmed by the details if you don't have a clear roadmap to follow.
Will Rogers never met me.
|
|
|
|
|
Hi,
How to hide print option for pdf files in document library in sharepoint 2007.
|
|
|
|
|
Hi
I have read so many questions on the internet about the 'microsoft.ace.oledb.12.0 provider is not registered' error and thought someone here might just help us out?
Suggested solutions so far include:
1. compile the solution to target 'x86 cpu'. this or leaving it as 'any cpu' will have the solution install in the win 7 OS but the error will not disapper. i tried enough times. If you change the target to x64, however, the solution does not install.
2. install 'AccessDatabaseEngine'. I downloaded and installed and nothing changed.
3. install 'AccessRuntime'. This too did not change the error message.
Basically, the error is the application runs but cannot connect or interract with the access 2007 database in win 7, but works perfectly in win xp.
I have learnt that x64 machines (vista, win 7) do not have drivers to run x86 applications (Access 2007). win 7 smartly creates a separate x86 Programs folder to install the applications, but still cant work with access 2007 database in the application.
Does anyone have a solution that can be packaged and distributed with the vb 2005 application to have the data side work?
a few suggestions that i also found include long winding procedures with iis7 which also only work in certain circumstances and arent really what you would instruct users to go through. I'll really appreciate a solutions that, say suggest a kind of dll to develop or download and distribute with the application to go round the x64 problem
thanks.
|
|
|
|
|
I understood from earlier discussions here the Access adapter/connector does not exist for x64, so there is nothing you can do about it so you must build your EXE for x86, not for "any CPU".
Assuming that is correct,If that doesn't suit you, your best bet probably would be a switch to SQL Server (possibly the Express version). And if you were to need existing data, either a backup or a copy/convert operation on an x86 system would be required.
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at them. modified on Thursday, December 2, 2010 5:54 PM
|
|
|
|
|
cyberexel wrote: I have learnt that x64 machines (vista, win 7) do not have drivers to run x86 applications (Access 2007).
Wrong way to say it. It's not a case of having drivers to run an application. It's that the application doesn't supply any 64-bit drivers. Drivers (.DLL's really) are loaded into the same process that calls them, i.e.: your application. You cannot mix 32 and 64-bit code in the same process, so you cannot have a 64-bit app interact with an Access (Jet) database.
You have to recompile your app as x86 only. There are no 64-bit drivers for Access, so you're database code won't work if you leave your app compiled as AnyCPU. AnyCPU will result in your application being JIT'd as a 64-bit app when run on 64-bit Windows and 32-bit when run on 32-bit Windows.
Your other option is what Luc said. Drop using Access and switch to SQL Server Express. SQL Server has drivers for both 32-bit and 64-bit Windows.
|
|
|
|
|
Thanks to both for the candid answers. I will redo in Ms SQL; it is just about 5 times the size of accdb!
|
|
|
|
|
Hi,
There is a windows service created and I am trying to start the service from service manager. I am getting an error stating that the service stopped unexpectedly after start. This is happening in Win Server 2008.Prior to that service worked fine in Server 2003.
Any ideas? Please help.
Thanks in advance.
modified on Thursday, December 2, 2010 7:35 AM
|
|
|
|
|
Hi,
which version of .Net did you develop the Windows Service ?
is the same version is installed on Win Server 2008 ?
|
|
|
|
|
Do you have error/exception logging implemented in your service? If yes check the logs.
I would also suggest you to check the event log for related entry. In most cases, the error will be logged here.
You can navigate to event log in Win 2008 Server by clicking Start->Programs->Administrative Tools->Event Viewer. Check entries in Windows Application Log.
If you still don't find the problem, the last option will be debugging the service which won't be required if you have proper exception/error logging in your service.
Let me know if that helps.
..Go Green..
|
|
|
|
|
It was developed in .Net 3.5.
I did check the log entries in event viewer and resolved the issue.
Thanks. 
|
|
|
|
|
I am glad that it helped you.
..Go Green..
|
|
|
|
|
Hi guys, i doing a project in which SSL is used. For SSL transmission X509Certificate is needed for Client and Server authendication.I am creating certificate using makecert tool
makecert -r -n "CN = "SampleProject" -sv SDKSamplePrivDeveloper.pvk SampleProject.cer
certificate is created sucessfully.
But i have an exception in server
sslStream.AuthenticateAsServer(serverCertificate,
false, SslProtocols.Tls, true);
[Exception]
An unhandled exception of type 'System.NotSupportedException' occurred in System.dll
Additional information: The server mode SSL must use a certificate with the associated private key.
I dont know what's wrong in certificate.I also provide the privateKey file in certificate
Some one tell me the reason ...
Thanks in advance
|
|
|
|
|
try with others protocols
SslProtocols.Tls
|
|
|
|
|
OK, can someone here confirm for me that MS screwed up here?
VS2008 allows you to use Debug.WriteLine to send data to debug stream where I can pick it up via a tool like DebugView.
VS2010 DOES NOT seem to allow this at all. I can see the debug data in the immediate window in the IDE but nothing appears to make it out past there...
If I run the EXE file I created in VS2010 as an administrator (right click and use the run as admin option) I can see the output written to the DebugView window but can't obviously catch any errors in the IDE and use that like normal.
VS2008 allows me to see the data in both areas without having to run as an admin at all.
If I start the process outside of VS2010 and see the debug in the debugview window then attach to the process using the IDE, the IDE horns in on the debug stream and stops it from going to debugview also.
UGH!
I really don't get this 'progress'.
BTW - I put this post here because I was really NOT sure where to put it... this is not a C# vs. VB thing.... Maybe an IDE thing but we don't have an area just for that
|
|
|
|
|
Sorry, I can't help you out as I don't use Debug.WriteLine at all.
However a little rant like this normally appears in Da Lounge to maximize reaction.
|
|
|
|
|
Luc Pattyn wrote: However a little rant like this normally appears in Da Lounge to maximize reaction
Regards,
Sathesh.
The best way to express one's gratitude to the Divine is to feel simply Happy..
|
|
|
|
|
Your question is little bit confusion for me whatever,
you should focus on the given link it is full with lots of thread
Link1[^]
and this one for know how to trace debug in VS
Link2[^]
Hope it will works for you.
|
|
|
|
|
Yes, I know how to use the statements themselves. I have been using them for years now.
The oddness seems to be specific to VS2010 and how it allows, or rather does NOT allow the output from these statements to leave the VS environment.
In previous versions of VS I used to be able to fire up a unified debug collection tool like windebug and gather all my debug statements in one log file This was helpful when trying to gather coordinated debug between several different processes together in one area.
Now it appears as if the IDE gets in the way and blocks that ability. You can see the output from Debug.WriteLine in the IDE area but it never makes it out into the standard debug stream like it used to so collecting it together from several instances of VS at once is not possible.
This also means that now I have to write my debug statements to provide a date and time component in them where collecting them in the windebug tool used to do that for me, and once again, used to do it from several instances at once.
|
|
|
|
|
So does anyone have any tutorials or white papers on how to begin with a registry cleaner, I am working on an all in one utility that wields a service controller and process controller to help with a friends pc repair shop, I know how to manipulate the registry to an extent I just dont understand how it compares version numbers or seeks old information in th registry with the programs that are installed and spews out what the errors are.
|
|
|
|
|
Hi guys i need to extract audio from a WMV file. I never try this kind of task before. So any one tell me how can i achieve this in .NET
|
|
|
|
|
ganesh_IT wrote: i need to extract audio from a WMV file
There's plenty of command-line tools that offer this kind of functionality. The easiest way would be to launch one of those from your own application.
ganesh_IT wrote: I never try this kind of task before
That doesn't entitle you to a walk-through. It's generally a good idea to research the topic and attempt something - that way you can ask more specific questions.
ganesh_IT wrote: So any one tell me how can i achieve this in .NET
There's an article over here[^], might be a good place to start your adventure 
I are Troll 
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
