|
Oh, I forget that point thanks to remind me dear 
|
|
|
|
|
|
thanks for these amazing resources
|
|
|
|
|
Forget about ArrayList, ArrayList is really very much old and you should focus on what C# now has. C# has List object, and it is primarily "managed" array. In static arrays, you have a static length of it. So, if you created an array of size, say 10, you will always have 10 indices to care of even if you store only 3-6 objects in it. Same case, if you want to add more you cannot since you are only allocated with 10 indices.
In List case, you can always grow the size or shrink it as needed. Such as,
var names = new List<string> ();
names.Add("Afzaal");
names.Add("Ahmad");
You cannot do the same in case of arrays, the above is similar to having the following,
string[] names = new string [] { };
names[0] = "Afzaal";
names[1] = "Ahmad";
To see what happens you can do the following,
Console.WriteLine(names.Length);
That will print "0", telling you that the array was empty and you cannot grow or shrink it on runtime. On the other hand you can easy do so.
The generic stuff really don't matter much in my opinion, you can do the same,
var list = new List<string> ();
var list = new string[] { };
But however, the helper functions are very much great in List objects as compared to the Array objects. The comparisons have been made for a lot of time, you can read any of other articles as well.
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
modified 3-Feb-17 7:39am.
|
|
|
|
|
Thanks afzaal I have cleared my concept 
|
|
|
|
|
Basically, don't use an ArrayList at all - it was superseded in V2.0 of the .NET framework when Generics were added to the C# language: and that was back in 2005! You should not be designing ArrayList into new developments unless you are interfacing with legacy code that requires them.
Use a List<T> instead.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Because arrayList has its own operatons on list different from array
|
|
|
|
|
Hi.
I'm using WebBrowser to display authenticated web page. I implemented the interfaces decribed in this post.
object obj = myBrowser.ActiveXInstance;
IOleObject oc = obj as IOleObject;
oc.SetClientSite(this as IOleClientSite);
string authHeader = "WWW-Authenticate: Negotiate\r\n";
myBrowser.Navigate(_URL, "", null, authHeader);
I'm using Negotiate so I can use also SSO. The authenticate method is implemented like this:
public int Authenticate(ref IntPtr phwnd, ref IntPtr pszUsername, ref IntPtr pszPassword)
{
pszUsername = Marshal.StringToCoTaskMemAuto("user");
pszPassword = Marshal.StringToCoTaskMemAuto("pass");
return S_OK;
}
It works well. But the problem is when I want to authenticate the user with different domain. This doesn't work:
pszUsername = Marshal.StringToCoTaskMemAuto(@"domain\user");
pszUsername = Marshal.StringToCoTaskMemAuto("user@domain");
I'm not able to display the page for users with different domains. It returns unauthorized.
I don't know what changes to make so it's working..
Thank you.
|
|
|
|
|
Forget about the code for a second; can you give us an example of which domain you would like to authenticate? See, if you're authenticating someone from, say, Microsoft, then their domain-server would have to trust[^] yours.
The network-name might not always the same as the domain that is used on the internet.
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
The app I'm connecting to, runs on our server. There is also web login to the server app. The users log in using domain with their username (domain\user1).
I'm not very familiar with this technology but I will look up necessary facts, if you need more info.
|
|
|
|
|
..so, the user opens a webpage on your webserver, logs in using a form? Can the user login using those credentials using a regular browser?
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Yes, the user can log in using the form on webpage with the given credentials. In the web form the user selects the domain, put down the username and password. As I was told the domain and the username are then put together like this "domain\username" when the logging is being processed.
That led me to conclusion that I should concatenate the domain and the username in the winforms app too. But I'm getting unauthorised.
So I thought that there is something else I should set..
|
|
|
|
|
kubiiik wrote: So I thought that there is something else I should set..
You should be able to sign in on your own website without modifications. The WebBrowser-control is "just" an instance of IE, nothing special.
The thing that threw me off was the reference to "other domains". You wouldn't be able to authenticate people from the domain our company uses, simply because it is outside the network.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Eddy Vluggen wrote: You should be able to sign in on your own website without modifications. The WebBrowser-control is "just" an instance of IE, nothing special.
Just to clarify, we do not display any login page in the webBrowser. If the user log in using regular browser, the log in page is displayed. But when using the C# winforms app, the log in is set in the app and used as string in the Authenticate method.
Eddy Vluggen wrote: The thing that threw me off was the reference to "other domains". You wouldn't be able to authenticate people from the domain our company uses, simply because it is outside the network.
I don't understand the domain users much (I had to google more info about it), but I think that the domain controller should handle the users (according to http://www.howtogeek.com/194069/what-is-a-windows-domain-and-how-does-it-affect-my-pc/[^]).
|
|
|
|
|
kubiiik wrote: Just to clarify, we do not display any login page in the webBrowser. If the user log in using regular browser, the log in page is displayed. But when using the C# winforms app, the log in is set in the app and used as string in the Authenticate method.
Thanks for that clarification
I was expecting windows-authentication, which would not require a special login.
kubiiik wrote: I don't understand the domain users much (I had to google more info about it), but I think that the domain controller should handle the users
Yes, but you won't be able to verify anyone outside your own domain.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
According to the new information I got, the server end has only implemented WindowsBasicAuthenticator, which ignores these domains.
But unless the server end implementation is updated, I will not know that for sure.
Anyway, thank you for your time
|
|
|
|
|
I recently installed Microsoft Visual Studio Community 2015.
When running my app in Visual Studio (developed with previous version of Visual c# as express edition 2005, 2008, 2010) , it's ending on unhandled exceptions rather than showing a message box with the exception info and continuing on as I was used to.
What options do I need to change to get it back to the behavior I'm used to (with Visual c# express edition 2005, 2008, 2010)?
Regards
Roberto
|
|
|
|
|
Since we have no idea what your code is doing, it is impossible to answer. You need to collect more information about where the exception occurs, and why.
|
|
|
|
|
Ok I think that what is doing the sw now is not important. Before (years ago), when I was creating the app and testing it (but this was common to any app created in the past), the environment Visualc# express edition 2010 was configured in a way that, in case of error, a popupwindow was showed besides the line where the code was halted because of a Runtime error. Popup Windows was giving some information, in some cases very exhaustive in some other less but useful anyway about the reason of the fault.The line of code itself was highlighted green (or some other color i can't remember). So I knew where the code had a problem (Runtime). Now the point of your question is exactly this. In the new environment I cannot identify neither the point nor the reason for the fault. The app exits and simply return an error code not so useful in my opinion.
Regards
Roberto
|
|
|
|
|
The information should all be provided by the debugger.
|
|
|
|
|
Check out the options under Tools -> Options -> Debugging -> General
Speed of sound - 1100 ft/sec
Speed of light - 186,000 mi/sec
Speed of stupid - instantaneous.
|
|
|
|
|
Ok I did this trying to follow suggestions found around on the net. None was working. So what should I check or uncheck in your opinion?
Regards
Roberto
|
|
|
|
|
Break all processes
Break when exceptions cross AppDomains
Enable the Exception Assistant
Speed of sound - 1100 ft/sec
Speed of light - 186,000 mi/sec
Speed of stupid - instantaneous.
|
|
|
|
|
And if nothing there helps, put an unhandled exception handler in your code and find out what is going on.
Speed of sound - 1100 ft/sec
Speed of light - 186,000 mi/sec
Speed of stupid - instantaneous.
|
|
|
|
|
Ok I set all exceptions around to break the app. It doesn't seem to work. But then I added this :
int j = 0;
int i = 3 / j;
and I had the usual behaviour with line "int i = 3 / j;" highlighted and the relevant exception display.
code is something like :
[DllImport("AVICAP32.dll")]
public static extern bool capGetDriverDescriptionA(
short wDriver,
string lpszName,
int cbName,
string lpszVer,
int cbVer
);
bool bReturn;
bReturn = MyAppCam.Capture.capGetDriverDescriptionA(x,strName,100,strVer,100);
I know that code is stopping on "bReturn = MyAppCam.Capture.capGetDriverDescriptionA ... "
Regards
Roberto
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
