|
I think the exception is saying that you need to specify the virtual list size.
listView1.VirtualListSize = 1000;
Once this property is set then I think you should be able to add new items.
Excellence is doing ordinary things extraordinarily well.
|
|
|
|
|
|
Hi All,
Do we have DirectX support in C#.Net?
If not ,do i need to install latest Directx SDK?
Please advice.
Regards,
Ashwath
|
|
|
|
|
Message Closed
modified 23-Nov-14 6:55am.
|
|
|
|
|
Thanks....
I went to the references,from there i found the following references,
Microsoft.DirectX.Direct3D
Microsoft.DirectX.Direct3DX
etc...
Does the availability of above references mean that when we install .Net framework in the computer,that time itself the references are added and i do not need to install the directx SDK.
Please clarify,
thanks,
ashwath
|
|
|
|
|
Message Closed
modified 23-Nov-14 6:54am.
|
|
|
|
|
Does DirectX libraries get installed when we install Microsoft Visual Studio 2008?
|
|
|
|
|
No. It's a separate SDK that you have to download and install manually.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001
|
|
|
|
|
Hi,
We have developed C# windows base application , we would like to make the UI
more posh with some graphis for all controlls at the same time we dont want
to use any third party controls to bring this. Does .Net Framework - 2005 or 2008 and C# supports this, if so how can i bring up galssy look for my UI.
we are using C# 2008 Express edition for development.
Thanks
|
|
|
|
|
sjs4u wrote: Does .Net Framework - 2005 or 2008 and C# supports this,
Yes. But you need to create custom controls and draw yourself on the screen. This is not a trivial task. If you can use WPF, you will get shiny UIs.
Best wishes,
Navaneeth
|
|
|
|
|
WPF can provide some good UI effects.
If you are still in the initial stages of your project, you can consider WPF as an option for your UI.
| There are only 10 types of people in this world — those who understand binary, and those who don't. |
|
|
|
|
|
Hi my friends .... I have been hacked my email address 2wice .... at first i just used some questions ... like what was your Pets name & like ... & i got it .... but this time even this one doesnt work ... i.e the hacker changed my question too ........... and i heard that there are softwares that retrieve my email account password ......... but they are too expensive for me ....... So any know how to retrieve my password by just writing C# code .... plz help me ... or if there is any software point me ....
Thank you.
|
|
|
|
|
No, there isn't.
It sounds like you're not in control of the server, so you're going to have to do what everyone else does, and call tech support.
|
|
|
|
|
Thanks for your help.. But what i lost is on my yahoo account .... and i heard that there are so many softwares that are being sold online.... didnt u heard about them? .... so what am saying is instead of buying that i can write my own software using C#.. bcoz it is costy for me to buy them
Thank you.
|
|
|
|
|
Noone here is going to help you hack your own Yahoo account. End of story.
Why? How do we know it's YOUR Yahoo account and not someone elses??
Have I heard of such tools - no, and do not care to, for obvious reasons.
Call up Yahoo and get it reset, legitimately, and it doesn't cost you anything.
|
|
|
|
|
hey ppls ... do u think am dumb!!!!!!!!!! ....... do u think i post a question to hack ppls account ........ @ least tell me other ways to get my account back .... as i told u ppls even my secret questions doesnt work .......... that is the reason i come here and ask u guys .... pllz help me .... I cant contact ma families and friends .......... and How can I call yahoo and reset my account with out no cost???? ... if it is possible too ... still help me
Thank you
|
|
|
|
|
Who's fault is it that you create remember your own security question answers??
If you can't call them, ever hear of "email"? Create another account, since they're free!, and email Yahoo's support and ask them.
Again, there is no tool to do what you want. If you believe there is, try sending them money for it and watch what happens!
|
|
|
|
|
Your argument is invalid, Yahoo has a process to recover password by simply answering the security question provided.
So we're only left with you asking for help hacking accounts. GO AWAY! You'll find no help here.
I know the language. I've read a book. - _Madmatt
|
|
|
|
|
Request to remove this poor child from this honorable forum.
|
|
|
|
|
I need to be steered in the right direction of some thread monitor code.
I forked my large multi-threaded chat server written in c#, running in mono on a linux box.
My software (I'm assuming) is having a sort of deadlock issue after a couple days. I have always been able to identify any problems in the past by seeing exceptions and/or obtaining the right information about what piece of code is causing what. Given the remoteness of the application and the silent deadlock, I am having a terrible time finding the source of the problem.
I have thought of a way I could write a piece of code that monitors all the the threads and the threads would report back to it after their cycles. That way the monitoring thread could keep tabs on which threads are idle, stalled or otherwise. I would just print this info to the console for review.
Please I am in need of your great guidance oh wise and smarter than me developers. I need some advice on where I should head, because I'm sure one of you has had a similar situation. This has plagued me for two months. My other version which runs for a different client on a windows box and has minor changes to the codebase, can run for months.
TIA
|
|
|
|
|
in situations like that, and many others, what I do is add logging code; these are basically calls to a lightweight log method emitting a single line of text with a lot of information, typically time of day, threadID, and a string that is passed to the log method, describing where in the code the log is happening.
I often log to a ListBox (in a WinForms app), to the Console (when running under Visual Studio), or to a file; and often a combination of those (ListBox/Console are fine while the app runs, file is OK to keep a record).
BTW: for file logging I typically use File.AppendText which means the file is always closed, and is intact, up to the last log message, even when the app crashes.
Having log files you can watch what was happening at or around the problem point, and compare the sequence of events with others.
Once you have a single log describing a failure, you can:
- run again till the next failure, and compare failures;
- add log statements in and around suspected areas in the code;
- add assertion statements (checking invariants, things that should be true, and only logging when they aren't);
- try and find ways to up the failure frequency, which also means the waiting period between failures goes down, so you capture more information in less time.
The overall philosophy is: improve observability.
So with a threading/deadlock problem, I would add log statements to every thread-related call (thread creation, thread joins, start and end of important methods, etc). I would generate as much as 1000 logs per second, if that is required.
This special way of debugging beats the regular breakpoint/single-step approach in that it is much more automated and a lot faster; it is essential to solve problems that take a long time to occur, and/or seem to be rather random.
BTW: it could be that you are facing another problem, here are a few candidates:
- not enough error handling: something is throwing without you noticing; make sure you have all the try-catches you need; put a try-catch in the staic Main() as a safety net; install an Application.ThreadException handler. Don't ever have an empty catch block, at least log the exception.
- running out of memory; logging Environment.WorkingSet periodically (with a Windows.Forms.Timer) could be very helpful (although it might miss a "large-object-heap" fragmentation problem.
- a thread synchronization problem: lacking a lock somewhere makes your app use an invalid combination of state variable values (these may be the hardest to figure out as they very much depend on timing).
|
|
|
|
|
Nice response Luc
I guess a lot of people (wether they are writing Multithreaded or not) don't include any/enough observability in their code, then when the crunch comes, whammo !
I tend to use a logging/library that when Im not actually monitoring/looking for something, is cheap, ie, consumes the barest minumim resources, and doesnt log the messages until I turn a level 'on' - that way its already in my code so I dont have to go back and add it later
cheers
'G'
|
|
|
|
|
Thanks.
I did a lot of embedded development, mostly with soft real-time requirements; logging was the first and best tool for debugging all kinds of problems then, and it still beats an interactive debug session except for the simplest errors (the ones an experienced programmer typically doesn't make  ).
For complex apps, I have my own log class with categories one can interactively raise and lower thresholds for; I include log statements from the very beginning, and whatever debugging code I add, I never remove it again (it is part of the code, part of the effort, why throw it out?)
|
|
|
|
|
Excellent response, Luc! 
It reminds me a bit of my former career designing automated test systems for missiles. The #1 rule of Testability: A Testable product is both Observable and Controllable. All electronic control systems use feedback; an open-loop system is inherently undesirable, as functional accuracy is limited to component accuracy without active feedback. But if a tester cannot see interior points in the circuit, and can't open the feedback loop to measure values inside, it is not possible to test the circuit. There also must be a means to force a change of state in the circuit and observe the results in order to make an effective test.
The same principle applies to software; if you can't observe the internal states, you can't expect to diagnose a problem when it occurs. Logging - not only errors, but the system states before and after a fault - makes diagnosing the cause of a problem far easier. In many cases, it probably is the only way to diagnose a failure.
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
|
|
|
|
|
Thanks Roger.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
