|
Add a Dropdownlist inside an ItemTemplate.
This[^] should help you out.
|
|
|
|
|
Hi,
my WCF service is running with threads, based on the ID value(for every ID value from database one thread will start when service starts), I want to pause a thread some time, and restart again.
End user will press the Button from the webapplication, then ID will pass to the WCF service. then that thread has to pause and restart.
Please help me, if any one knows,
Thanks in advance
Murty
|
|
|
|
|
dwadasi wrote: want to pause a thread some time, and restart again.
The thread Suspend method is now obsolete.
However, you can consider using the ManualResetEvent class for this kind of operations.
Be sure to ensure data is locked during such type of operations.
|
|
|
|
|
dwadasi wrote: my WCF service is running with threads, based on the ID value(for every ID value from database one thread will start when service starts), I want to pause a thread some time, and restart again.
What happens if they never restart it?
What happens if the server bounces (stop then start) after the user pauses it?
|
|
|
|
|
|
This is the wrong forum. If you want some reasonable feedback then write an article and post it for publication as described in the guidelines[^].
Unrequited desire is character building. OriginalGriff
I'm sitting here giving you a standing ovation - Len Goodman
|
|
|
|
|
Hi,
I have chosen for my final year project to make an ASP/C# web application as well as its mobile version using VS2008. Please guys if you know how to make a mobile web application and what are the tools needed beside VS2008.
Cheers,
|
|
|
|
|
1. This is not the ASP.NET forum.
2. You really need to learn to do your own research if you expect to succeed with this project.
3. This[^] is the obvious place to start.
Unrequited desire is character building. OriginalGriff
I'm sitting here giving you a standing ovation - Len Goodman
|
|
|
|
|
|
Hi,
I have a VS2005 project for Windows CE 5.0. After I migrate it to VS2008, I want to downgrade to .NET 2.0 for the backwrad compatability. However I can't find "Target Framework" in the project properties for me to select. How do I downgrade it? Thanks!
Best,
Jun
|
|
|
|
|
You don't. The "Target Framework" option didn't come around until Visual Studio 2010.
|
|
|
|
|
I use VS 2008 C# Express regularly, and I set "Target Framework" to ".NET Framework 2.0" all the time... (the other choices being 3.0 and 3.5).
Luc Pattyn [My Articles] Nil Volentibus Arduum
Fed up by FireFox memory leaks I switched to Opera and now CP doesn't perform its paste magic, so links will not be offered. Sorry.
|
|
|
|
|
Really? Has it been that long already that I've forgotten about it?? 
|
|
|
|
|
It turns out that the IDE treats desktop and device apps differently. With a device app, you can access the main menu "Project->Change Target Platform..." where you can select among various mobile platforms.
Best,
Jun
|
|
|
|
|
For the last 7 years I’ve been doing all of my (professional) programming in VB. Now I want to make the long overdue leap to C#.
For no real other reason than I have been doing a fair bit of Objective-C in my spare time and I'm sick of syntax hopping for the first couple of blurry hours on Monday morning.
I'm not looking to start another C# v VB discussion, and I’m not looking for the noobie VB -> C# conversion charts. What I’m asking is from all you C# gurus what little tricks, tips and advice can you offer a non-noob, who really should have worked in both platforms from day one?
modified 22-Jan-12 19:20pm.
|
|
|
|
|
The language capabilities are basically the same. C# is less verbose and needs more semi-colons and braces; the one thing I appreciate is VB's Handles keyword. New goodies (anonymous delegates, LINQ, lambdas, ...) typically get introduced in C# first, so that should not pose any problems.
In practice the main differences I'm aware of are:
1. VB is not very strict by default; you can get away with a few things other languages don't allow. So you might want to add option strict on and the like (if you haven't done so already) and retest, before engaging in a conversion.
2. There are a number of VB-specific namespaces (e.g. Microsoft.VisualBasic.Compatibility), which you could continue to use in another language, although I wouldn't recommend that.
3. Visual Studio does a couple of special tricks to ease the VB->VB.NET transition. Example: all forms are auto-instantiated.
4. Some environmental aspects are different, e.g. Visual Studio offers a splash screen out of the box in VB.NET, not in C#. There probably are a few more issues of this kind, I don't know.
In conclusion, if your code started as VB6, was then made to work in VB.NET, then I'd say it deserves some refactoring; and if it is quality VB.NET code, I wouldn't expect real issues.
|
|
|
|
|
Luc, thankyou very much for taking the time to respond.
I think my ignorant self may have been ambiguous, sorry.
What I should have asked is Making the switch from VB.net to C#.
I sometimes forget there was a vb world before .net
Sorry, but thanks again.
p.s. i've just edited the title
|
|
|
|
|
No problem, I think I covered both cases in one anyway, while assuming you already had VB.NET, given your choice of forum.
|
|
|
|
|
|
A few months ago I finally made the same switch, and I don't regret it. The few things that took a bit of time to get used to:
- A few type conversions that are handled automatically by VB need to be explicit in C#. It does however force you into better programming.
- If you are working with forms: Forms are instances of the Form object (well, as they should be in OOP). The default form you get in VB however is static.
- If you're working with Visual Studio: use the latest one (2010); in older versions the intellisense felt a bit slower in C# compared to VB (might be just a 'feeling').
Good luck.
|
|
|
|
|
So I am trying to learn , and decide to look at BYTE .
What it is is clear , but why I might use it in code is not clear.
Maybey I could trouble someone to write a tutorial example that may highlight the value
of knowing what a byte is. hope this question is appropriate.
I probably clean up nice.
|
|
|
|
|
See here[^] for some basic information. You would use it when it is appropriate in your code, but only the context of the program can help you decide when that is.
Unrequited desire is character building. OriginalGriff
I'm sitting here giving you a standing ovation - Len Goodman
|
|
|
|
|
a byte is a small integer number, much smaller than an int. For a single variable, it probably isn't important to save a few bytes of memory. It can be most important when you either need millions of variables (e.g. in an array), or when you have a data structure (a C# struct) that must match either a file structure or a native data structure (e.g. when calling a Win32 function).
|
|
|
|
|
Thanks I like your expanation and appreciate your time.
I probably clean up nice.
|
|
|
|
|
A nice example of working with bytes is imageprocessing. Each pixel of a bitmap is represented by a byte for red, one for green, one for blue (optional one for transparancy), as each of these can take a value between 0 and 255. A 640*480 24bit (RGB) bitmap then takes less than one kb of memory.
If you would use 32bit integers to represent all these values that can not be greater than 255, you would end up with with four times the memory usage (whereof 75% empty).
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
