16,004,761 members
Sign in
Sign in
Email
Password
Forgot your password?
Sign in with
home
articles
Browse Topics
>
Latest Articles
Top Articles
Posting/Update Guidelines
Article Help Forum
Submit an article or tip
Import GitHub Project
Import your Blog
quick answers
Q&A
Ask a Question
View Unanswered Questions
View All Questions
View C# questions
View C++ questions
View Javascript questions
View Visual Basic questions
View .NET questions
discussions
forums
CodeProject.AI Server
All Message Boards...
Application Lifecycle
>
Running a Business
Sales / Marketing
Collaboration / Beta Testing
Work Issues
Design and Architecture
Artificial Intelligence
ASP.NET
JavaScript
Internet of Things
C / C++ / MFC
>
ATL / WTL / STL
Managed C++/CLI
C#
Free Tools
Objective-C and Swift
Database
Hardware & Devices
>
System Admin
Hosting and Servers
Java
Linux Programming
Python
.NET (Core and Framework)
Android
iOS
Mobile
WPF
Visual Basic
Web Development
Site Bugs / Suggestions
Spam and Abuse Watch
features
features
Competitions
News
The Insider Newsletter
The Daily Build Newsletter
Newsletter archive
Surveys
CodeProject Stuff
community
lounge
Who's Who
Most Valuable Professionals
The Lounge
The CodeProject Blog
Where I Am: Member Photos
The Insider News
The Weird & The Wonderful
help
?
What is 'CodeProject'?
General FAQ
Ask a Question
Bugs and Suggestions
Article Help Forum
About Us
Search within:
Articles
Quick Answers
Messages
Comments by Bruno Tagliapietra (Top 18 by date)
Bruno Tagliapietra
22-Apr-14 10:37am
View
Reason for my vote of 5 \n Interesting to point that out!
Bruno Tagliapietra
28-Sep-13 8:55am
View
Reason for my vote of 5 \n Funny and concise :)
Bruno Tagliapietra
1-Jun-11 12:51pm
View
you're aiming moon shooting with a slingshot... totally wrong man.
try here
http://www.learnwebdesignonline.com/css-tutorials/verticalmenu.htm
Bruno Tagliapietra
27-Apr-11 8:52am
View
linq is c# not sql, you have no aliases. If your method return type is List<TypeName> you must return a list of TypeName, not a list of anonymous type. So in your select you should do something like "... select new ASX_D{ PublicProperty1 = value1, publicField = value2, }" ... ...
Bruno Tagliapietra
23-Apr-11 20:55pm
View
"a timer will never be garbage collected while it is active" -- this sentence is false. You should correct it
Bruno Tagliapietra
23-Apr-11 20:45pm
View
That's true. So this is not a solution... Ok I'm changing it.
Bruno Tagliapietra
23-Apr-11 20:34pm
View
Deleted
I disagree too. Msdn says about System.Threading.Thread "As long as you are using a Timer, you must keep a reference to it. As with any managed object, a Timer is subject to garbage collection when there are no references to it. The fact that a Timer is still active does not prevent it from being collected.".
So your claim "a timer will never be garbage collected while it is active" must be false... or msdn must be wrong.
http://msdn.microsoft.com/en-us/library/system.threading.timer.aspx (the first "Note" in Remarks)
Bruno Tagliapietra
23-Apr-11 3:50am
View
Try asking your computer "Can I have that damned number??? ... please."
I mean, be more clear posting your questions please.. otherwise you'll get no answers just because it's impossible to give one
Bruno Tagliapietra
23-Apr-11 3:48am
View
http://www.microsoft.com/learning/en/us/certification/cert-overview.aspx
Bruno Tagliapietra
23-Apr-11 3:10am
View
Thanks. But if you wanna use timers and you're dealing with a winform application, the best choice would be System.Windows.Forms.Timer, just because it runs on the UI thread.
Bruno Tagliapietra
23-Apr-11 3:04am
View
Sorry, I wasn't clear enough, the matter is only with events and delegates.
GC can deal correctly with most of circular references (althought it should be better to avoid them whenever possible, that means: first declare static, otherwise make it instance-dependent).
However, it's a known fact that the GC has trouble sometimes in circular references involving events and delegates.
I wish I'd have a little more time to spend on this at the moment... Probably we should have a look to the ildasm of a simplified version of that code.
Bruno Tagliapietra
22-Apr-11 17:37pm
View
Deleted
That can't be done in Winforms.. You have to use WPF. Or, if you have to stick with .NET 2.0 or previous, GDI+
Bruno Tagliapietra
22-Apr-11 16:43pm
View
Deleted
I call TestCollectTimer.Test() in a button_click event handler, and it calls MessageBox.Show almost immediately...
Bruno Tagliapietra
22-Apr-11 16:30pm
View
I guess the error isn't firing in this method you posted here: you're reading, there's no serialization involved
Bruno Tagliapietra
22-Apr-11 12:35pm
View
Probably, it's me... to my knowledge, you can't call any SOAP service from a Silverlight client in a synchronous way.
But someone says you can:
http://www.codeproject.com/KB/silverlight/SynchronousSilverlight.aspx
read his article, try his code and/or ask him directly
Bruno Tagliapietra
22-Apr-11 11:46am
View
The problem under the hood is that Silverlight can't call web services synchronously.
You must access the service asynchronously.
Have a look here for example http://msdn.microsoft.com/en-us/library/ms730059.aspx
Bruno Tagliapietra
22-Apr-11 10:04am
View
try sending code in a zip file at bruno.tagliapietra@gmail.com
if you're sending a whole solution folder, "Clean" away the exe files from visual studio first.
Bruno Tagliapietra
21-Apr-11 14:31pm
View
The methods probably do the same job the operators += and -= do in c#.
Try using it thinking like this.
Show More