|
Push your processes into a Stack and kill them when you're done in the same order you pop them from the Stack.
|
|
|
|
|
Actually a better method is to use the COM Excel application Quit method. You can also set the DisplayAlerts property to true or false depending if you want to get prompted for unsaved files.
Thank you for your input.
Glenn
|
|
|
|
|
Hi guys, i try to send data directly to host MAC address(without using IPAdress). I am not a expert in network programming am just a beginner.
In my search i found some ideas, that is we can use
"SocketType.Raw" in socket to achieve this. But i cant understand it.
Another thing is i need to acheive this without NDIS Protocol Driver.
somebody pls explain me how to do it...is there any class or utility is avilable in .NET.
Thanks in advance
ganesh_IT
modified on Monday, December 13, 2010 4:53 AM
|
|
|
|
|
I think you should Google send raw Ethernet packet
|
|
|
|
|
Why are you trying to do this? Perhaps if you explained the problem you are trying to solve, we could offer alternatives.
|
|
|
|
|
You can't use the MAC address for application level comm. There are no application-level protocols that work with the data link layer.
So you're trying to do this with a protocol driver? Forget it - not possible.
What are you attempting to do with this?
|
|
|
|
|
I am trying to do this for a academic project.
Why we cant access the link layer.
What i need to do for done this project explain me i can achieve this....
Thanks in advance
ganesh_IT
|
|
|
|
|
I didn't say you couldn't get at it. I said there are no application level protocols that can.
You'd have to talk directly to the device driver through any interface it supports, but probably using DeviceIo calls. Without documentation on the driver itself, you'll get absolutely nowhere very fast.
ganesh_IT wrote: What i need to do for done this project explain me i can achieve this....
Achieve what? You haven't said anything about your project is about at all or why you think you need Link layer access to the NIC.
|
|
|
|
|
Hi,
I am using the App.Config in my windows form application.. I want to to ask if it will be complied within the EXE or I have to copy it in my my setup project?
|
|
|
|
|
It's a separate file.
In your Debug/Release folder it's named "<yourapp>.exe.config".
Cheers
I don't like my signature at all
|
|
|
|
|
This is a absolute basic question on the foundations of .NET applications. As has been noted before you have asked a considerable amount of basic questions and you have been given the advice to read some books or take a class and learn the basics properly, not stumbling around. Please take this advice.
I know the language. I've read a book. - _Madmatt
|
|
|
|
|
Hi
I have a VS 2008 solution with two projects inside and I am want to deploy it... both will be deployed in a folder called C:\Program Files\My Projecr in Project-1 and Project-2 folders..
Both projects use shared assemblies like the MySQL DLLs.
Do I have to copy the same assemblies twice? once in Project-1 and again in Project-2?
|
|
|
|
|
Typically, shared assemblies are placed in the GAC, only a single copy. You can also create a common folder to place the shared assemblies for your applications but you will need to direct the .NET framework as to where to find them.
You may want to read through this
How the Runtime Locates Assemblies[^]
I know the language. I've read a book. - _Madmatt
|
|
|
|
|
so how can I place all in Common folder in my application folder and redirect the .NEt framework? can you please guide..
hanksT
|
|
|
|
|
Did you even read my response? Did you follow the link?
Stop asking questions here and go learn 
I know the language. I've read a book. - _Madmatt
|
|
|
|
|
Put these dll's in the GAC.
You can share them across both projects.
You dont need to copy these DLL's if they are already available in the GAC.
The funniest thing about this particular signature is that by the time you realise it doesn't say anything it's too late to stop reading it.
My latest tip/trick
Visit the Hindi forum here.
|
|
|
|
|
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.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
