|
Well you think the problem is the database?
|
|
|
|
|
It may be that it isn't suited for your environment, but that's something you'll have to determine.
|
|
|
|
|
What exactly do you mean with "for your environment"? What should I do in that case? I google for an answer, but I didn't find one..I changed the folder destionat and it worked, but I need in "Program Files"..
|
|
|
|
|
DPaul1994 wrote: I need in "Program Files"..
No. That's the wrong place. (If Windows) try the ProgramData or %userdata% directories.
|
|
|
|
|
Please explain "better"
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
"suited for your environment"
(PIEBALD carefully balances on a fence.)
|
|
|
|
|
Looking at the fence, I'd say it is pretty sturdy
The database is not chosen only based on environment; having a server would solve the problem with the file-system rights, but would also be quite a bit overkill if the application is comparable to, say, KeePass.
By the way it reads, it would be data that is accessed by multiple users simultaneous. In that case, SQLite definitely is not suited for the task, as only one person can have a file open for writing at a time.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Simple; put the databasefile in a location where EVERYONE can access it. If the user has no rights, he/she will not be able to modify the file's contents, it's that simple.
As PIEBALD suggested, you could opt for a database-server. Those usually connect over TCP/IP, and have their own authentication - one that is not determined by the file-system.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
When you installed your database, did you by any chance install it into your program directory? You know, the directory that's normally protected so that software can't do malicious things to your system.
|
|
|
|
|
I have been trying all day to figure out why in one of my C# projects in Visual Studio 2013, .NET framework 4.5 I cannot find System.DirectoryServices.ActiveDirectory. I try to add it as a reference but it does appear in Reference Manager. I have been searching all day on how to resolve the issue and I cannot find an answer. I need some help please. I am out of options.
The only thing I can guess is that using System.DirectoryServices.AccountManagement replaces System.DirectoryServices.ActiveDirectory.
Time is the fire in which we burn.
|
|
|
|
|
Your post appears to be screwed up. You tried to add a reference and the .DLL does NOT show up?
That's because it doesn't exist. On .NET 4.5, the available references are System.DirectoryServices.dll, System.DirectoryServices.AccountManagement.dll and System.DirectoryServices.Protocols.dll.
I believe the one you're looking for is System.DirectoryServices.dll. It contains the NAMESPACE System.DirectoryServices.ActiveDirectory.
|
|
|
|
|
You are correct. It is screwed up. I was trying to say "does NOT appear in Reference Manager".
I tried adding System.DirectoryServices.dll and the namespace system.DirectoryServices.ActiveDirectory now appears. Thank you very much.
Time is the fire in which we burn.
|
|
|
|
|
I found the object browser in VisualStudio to be very helpful.
I put System.DirectoryServices.ActiveDirectory in the search bar and get:
namespace System.DirectoryServices.ActiveDirectory
Member of System.DirectoryServices
There are strangers on the Plain, Croaker
|
|
|
|
|
That is exactly what I tried and it did not work. In any case, the issue is resolved so thank you for your help.
Time is the fire in which we burn.
|
|
|
|
|
For an Active Directory utility I wrote, I have references to:
C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\System.DirectoryServices.dll
C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\System.DirectoryServices.AccountManagement.dll
C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\System.DirectoryServices.Protocols.dll
|
|
|
|
|
I managed to write what I needed with those references as well. Thank you for your reply.
Time is the fire in which we burn.
|
|
|
|
|
hey all im using visual studio 2015 rc right and i want to connect a sql table to visual studios, im watching a tutorial on youtube on the video the guy (uses 2010)goes to add new item > local database / and i dont have that option? is it removed? or has the name changed?
modified 21-Jul-15 6:30am.
|
|
|
|
|
Are you using the same version as the person in the video?
There will probably be a small difference between the free and the full version.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
no im using 2015 rc he is using 2010 , i wanted to know how do i do it on 2015
|
|
|
|
|
"release candidate"?
Of the community edition?
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
i think so , its the 2015 rc but iguess its the comunity one, (free one)
|
|
|
|
|
The free edition is of course limited in functionality.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
This is not a C# issue. However, I just tried it on VS 2013 Express and the option is not available, although on VS 2010 Express it is. I suggest you contact Microsoft.
|
|
|
|
|
Doing some research on techniques for passing a variable length list of parameters of different types, I came across this: [^]
"Another possible solution that doesn’t require you to create a new type is using a Func delegate. Like so:
Func<int, string, Tuple<int, string>> c = Tuple.Create;
var list = new List<Tuple<int, string>>
{
c(1, "apples"),
c(2, "kiwiws"),
};" I've never seen the Tuple.Create method used in this way, and I am real curious about what is going on under the hood.
Appreciate hearing your thoughts on this.
thanks, Bill
«I want to stay as close to the edge as I can without going over. Out on the edge you see all kinds of things you can't see from the center» Kurt Vonnegut.
modified 20-Jul-15 16:10pm.
|
|
|
|
|
Hi Bill,
there's not a lot of magic going on there. c is basically declared as an alias for Tuple.Create(int, string). You could remove the declaration of c and replace c(.., ..) by Tuple.Create(.., ..) or new Tuple(.., ..). Whether or not this is more readable or in just any way better is up to personal taste I guess.
cheers, Sascha
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|