suppose i have a store procedure which has one out type parameter and out type parameter value is set inside store proc so when i will call that store proc by EF code first then how could read the out type parameter value by EF code first ?
looking for a small sample. i search google a bit but found no example. thanks
Seriously? I just read your question about what the difference is between Agile and Scrum. Have you heard of Google? You have been on this site long enough to know that you should at least think of doing some research beforehand yourself. This is a simple question for you to look up and I would strongly recommend that you learn to do the most basic searches yourself.
I asked a similar question a while back and never really got an answer, so I'll try again...
I have an application that has a component that works like DropBox. The user puts a file into a folder and it's copied to the server. Then all other users clients will download the file.
I need to determine the correct way of getting the file onto the server. The file will either be copied to the server or FTP'd in.
I need to determine when to use FTP. Obviously if the user is not connected to the network, then the file needs to be FTP'd in. For example, if the user takes their laptop home or on the road - away from the office - they they are not "connected" to the network and FTP needs to be used.
However, if the user is sitting at a desk in the office, then they are "connected" to the network.
The question is: How do I make the determination to FTP the file or just copy it? How can the app know if it's directly connected to the network?
One way you could accomplish this would be to check the DNS resolution of the server. If it resolves to an internal address, then the client is local and would be capable of performing a direct copy.
You could also just simply try the copy, or a less intensive get directory listing using the file path in your application. If that fails, failover to ftp transfer.
Is ftp available both internally and externally? If so, it would probably be simpler to utilize it for both transfers. It seems to me that it really wouldn't matter how the file got to the server as long as it was on the server.
Overkill is implementing more than one server and switching on detection of a network.
Just FTP it and you don't have to worry about the connection type at all.
Checking DNS resolution is probably not a good idea. DNS results are normally cached. Checking for active known company gateway addresses is probably a better bet, but if you just implement FTP, who cares?