|
Roger Wright wrote: my work PC has mixed feelings...
I know what would cheer it up... 
|
|
|
|
|
How to use C # to implement a user management module, the main function of the user add and remove.
|
|
|
|
|
1) The title of your message doesn't say anything about your problem. Every message in this Forum is about C#.
2) A "user management module" could be a lot of things. I have no idea what specifically you need help with.
3) What have you tried so far? Where is it giving you problems?
CQ de W5ALT
Walt Fair, Jr., P. E.
Comport Computing
Specializing in Technical Engineering Software
|
|
|
|
|
I know this is not a big problem, but I'm not familiar with C #, so I do not know how to connect to the database.
|
|
|
|
|
Are you trying to add and remove SQL Server users? Use System.Data.SqlClient.SqlCommand to execute commands against SQL Server and get back results. Google for "SQL Server create user", "SQL Server 2005 create login" and the like and you'll come across which commands you need to perform the SQL Server operations. You might also consider SMO, but that sometimes has problems depending on the version of SQL Server you are using. Some other tips:
*SqlConnection (a C# class available via the .Net Framework) will help you connect to the database.
*SqlConnection requires a connection string. Use SqlConnectionStringBuilder (another C# class) to create one.
*Make sure you have SQL Server Management Studio installed and you are able to browse a database using it (I am assuming you are using SQL Server since you didn't mention what database you are using).
Play around with that stuff a bit. It might take you some time to get things working, but that's all part of the learning process. Ask us when you have SPECIFIC questions, after you've already tried searching and trying things. Good luck.
|
|
|
|
|
|
Make Up Forever wrote: user add and remove
Manager.Add(user);
Manager.Delete(user);
Why is common sense not common?
Never argue with an idiot. They will drag you down to their level where they are an expert.
Sometimes it takes a lot of work to be lazy
Individuality is fine, as long as we do it together - F. Burns
|
|
|
|
|
Hi!
I'm testing the filecopier application to move, copy, delete...files from one directory to another directory. But when i write the nested class FileComparer in class frmFileCopier to compare 2 filelist, it has an error:
Error1 'FileCopier.Form1.FileComparer' does not implement interface member 'System.Collections.Generic.IComparer<System.IO.FileInfo>.Compare(System.IO.FileInfo, System.IO.FileInfo)'.
Anyone helps me?
Thanks
The code
public class FileComparer : IComparer<FileInfo>
{
public int Compare(FileInfo file1, FileInfo file2)
{
if ( file1.Length > file2.Length )
{
return -1;
}
if ( file1.Length < file2.Length )
{
return 1;
}
return 0;
}
public bool Equals(FileInfo x, FileInfo y) {
throw new NotImplementedException( );
}
public int GetHashCode(FileInfo x) {
throw new NotImplementedException( );
}
}
|
|
|
|
|
assuming you have all the necessary using statements, that code looks fine by me.
Of course, as is, all it may help you achieve is sort a collection of FileInfo by file length.
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read formatted code with indentation, so please use PRE tags for code snippets.
I'm not participating in frackin' Q&A, so if you want my opinion, ask away in a real forum (or on my profile page).
|
|
|
|
|
Can you show us all the code from that file? I suspect there is some sort of name clash or something funky like that. The class as it is seems fine.
|
|
|
|
|
I found that i had some mistakes in early code. The class is fine.
Thanks for answers! 
|
|
|
|
|
Hi all,
I've been trying to determine a good reason why one would use .TableName when the name of the DataTable variable is required anyway and .TableName is optional. Seems that having spent 10 minutes googling, gave me good enough reason to post here what seems like should be an easy question to answer......
I'm assuming it is the same type of situation one would encounter using ProEngineer (CAD). One could name a part with its part name (which would be the file name) and also have an optional "common name". So you could have 012569.prt which has a common name of Bolt. However, in my opinion, have different nomenclature for the same item is usually a "state of confusion" waiting to happen.
Thanks!
|
|
|
|
|
Remember that a DataTable was originally introduced as part of a DataSet, which allows a hierarchical linkage of tables (or you could just bundle several tables together in one if you liked). The TableName allows you to do things like search for the table in the DataSet.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
My blog | My articles | MoXAML PowerToys | Onyx
|
|
|
|
|
0) In case of a collection of them.
1) For when one is passed into a method.
etc.
|
|
|
|
|
You can't do that with the variable?
|
|
|
|
|
|
PIEBALDconsult wrote: Try it.
Yes, I knew this would be coming. One can certainly add a table to either a collection or use it in a method without having a formal name (but I don't think that is what you meant, is it)
public class Tables
{
public DataTable tblTest1;
public DataTable tblTest2;
public DataSet dsTables;
public Tables()
{
dsTables = new DataSet();
tblTest1 = new DataTable();
tblTest2 = new DataTable();
dsTables.Tables.Add(tblTest1);
dsTables.Tables.Add(tblTest2);
}
public void ShowTables()
{
DataTableCollection tables = this.dsTables.Tables;
foreach (DataTable tbl in tables)
Console.WriteLine(tables.IndexOf(tbl).ToString());
}
}
public static class Program
{
static int Main(string[] args)
{
Tables coll = new Tables();
coll.ShowTables();
Console.WriteLine();
Console.ReadLine();
return 0;
}
}
granted, having the foreach execute on
Console.WriteLine(tbl.TableName);
seems a bit more useful at first glance, so I guess I have my answer.........
|
|
|
|
|
Hi
I'm creating a desktop application for an old age home as a B.Tech project. This app needs to serve as a portal where users log in once to the application, and from there on gain access to their facebook and email accounts. When users decide to access Facebook, it shouldn't ask them for login details again, it should simply sign them in using a single sign on approach. I'm storing all my users' details (incl. Facebook email addresses and passwords) in a SQL 2008 database. And I'm using the Facebook Developer Toolkit from Codeplex[^] to create this desktop facebook application. Any hints on how I would proceed?
|
|
|
|
|
I'm not really sure what your question is here. It sounds like you've got the basics of a design sorted there. What exactly do you need help/advice with?
"WPF has many lovers. It's a veritable porn star!" - Josh Smith As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
My blog | My articles | MoXAML PowerToys | Onyx
|
|
|
|
|
In simple terms; How would I get users to log in to facebook using their facebook information from the database? Without being hassled by a facebook login page? Almost like automatically feeding login information into the facebook website (if I can use that as an example).
|
|
|
|
|
Remember that a web page just transmits data over HTTP. All you'll need to do is simulate the sending of that information for them.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
My blog | My articles | MoXAML PowerToys | Onyx
|
|
|
|
|
I'm guessing I need to use HTTP POST and GET requests here? I'm not very familiar with these. Also, I'm using a desktop application with a WebBrowser control, so I would probably need to use WebRequest.Create?
|
|
|
|
|
Please tell me how I would do this? Would I use WebRequest to construct a custom request?
|
|
|
|
|
I've created a few ASP.NET Web Service Applications. When you create one, it sets an attribute above the main service class which has a property, Namespace, that gets defaulted to http://tempuri.org/. According to MSDN, that default namespace should be changed:
It is highly recommended that this default namespace, which is http://tempuri.org, be changed before the XML Web service is made publicly consumable. This is important because the XML Web service must be distinguished from other XML Web services that might inadvertently use the namespace as the default (<http://tempuri.org/>).
What I want to know is the real purpose of this namespace and why it is important. How does that namespace help distinguish services? Is it if they are installed to the same folder on the server, it will prevent a clash of some sort? Don't you still need to specify the location of the service in any web service requests (e.g., "mydomain.com/Service1.asmx" or "mydomain.com/Service2.asmx")? And shouldn't that prevent any clashes?
Any illumination you could provide would be appreciated.
|
|
|
|
|
Perhaps this[^] (from tempuri.org) might help to explain why.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
My blog | My articles | MoXAML PowerToys | Onyx
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
