|
How can i learn OOPS concepts in a easy way to get the grip over the subject and use it in my daily coding life.
|
|
|
|
|
|
That was Object Oriented Programming concepts.
|
|
|
|
|
I know, hence my comment: it's OOP not OOPS. And did you follow the link I gave you?
|
|
|
|
|
Thanks Richard. I am getting an error while trying to opening the link it is showing error message as I am trying to open it from Google. Could you please suggest me another link so that it'd be grateful for me to learn.
|
|
|
|
|
|
|
Dear All,
**Actualy, I am a student and i want to join course of WCF And Web API But Friends I am Totally confused WCF And WEB Api is Different or Similar .Can I join the Both Course Of Join Only One Course (WCF and Web API).** 
|
|
|
|
|
You can find the answers you seek quite easily just by Googling for "difference between wcf and web api".
|
|
|
|
|
|
Your post is completely unreadable. Don't copy and paste the text from the web page. Copy and paste the actual code that threw the exception and put it inside PRE tags.
|
|
|
|
|
sOutput1 = "<td> <input type='text' name=DEPT maxlength = '4' value="
sOutput2 = qresults("DEPT")
soutput3 = "></td>"
Response.write (sOutput1 + soutput2 + soutput3)
(I really didn
|
|
|
|
|
The original post ended up in 4 columns. When the formatting gets all weird compared to a standard post I cannot assume I have all the information intended. To you, it looks fine because you are the only person who saw the screen and you are the only person who knows what to expect in the copy'n'paste.
Other people who have not seen your screen do not know what to expect.
You don't show the definitions of the sOutput1, soutput2 or soutput3 so assumptions have to be made.
If your code snippet was a copy'n'paste job, not typed by hand, try it this way
Response.Write(String.Concat(sOutput1, soutput2, soutput3))
|
|
|
|
|
Try to replace it with "+".
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
nope.. same message with the '+' instead of the '&' (but thank you for the suggestion!)
|
|
|
|
|
You're still using ADODB in a .NET application; you should look at switching to ADO.NET[^] instead, which has much better support.
Using ADO.NET for beginners[^]
Migrating from ADO to ADO.NET[^]
The problem is most likely that ADO is returning an ADODB.Field object, which can't be used with string concatenation. If I remember correctly, you need to access the field's Value property, and convert that value to a string:
sOutput2 = Convert.ToString(qresults("DEPT").Value)
You should also specify the types of your variables when you declare them:
Dim sOutput1 As String
Dim sOutput2 As String
Dim sOutput3 As String
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Thank you! The .value was it!!!!!!!! Wahoo!! I can finally finish this project that has taken way too long... 
|
|
|
|
|
This is classic ASP code, you can't just put it on an aspx page and expect it to work. You'll need to rewrite using c# (or vb.net which might be more familiar to you) and ADO.net
|
|
|
|
|
Hello,
I am not quite sure but using + operator will work for string.Please try and keep us updated
|
|
|
|
|
I have a scheduling service, which is a little WCF library hosted in a Windows Service, for the robustness of restarting on failure, and unattended startup. I have a small WPF GUI for both these services, to stop and start the host, and to force processing in the WCF, that normally only occurs every hour or so (Polling Timer #1), then to monitor a DB table I log events to. So, I have two processes running here, The Host (Windows Service), and the GUI, where the GUI is only supposed to run when needed, and the host runs constantly to ensure that the WCF is always able to do its hourly processing. Both processes are constantly using the event logging table in the DB.
I have had a wonderful learning experience (to keep things polite) in ensuring the GUI is always up to date, and responsive. This means the enabling and disabling of commands based on the service status, e.g. the "Start" button is enable based on whether the Windows service is running or not; then a TextBlock that shows the current status of the WCF, e.g. "Idle", "Polling", "Processing". Also, in the central/default view of the GUI, is the DataGrid that displays the contents the logging table (Polling Time #2), and I have a few methods where I wait on a Task that may time out (using a kludgy little util method, not async/await). After a hard few days, I have managed to slightly clear up what was an insane spaghetti mess of Timer, Task, and event threads and deadlocks.
I'm now trying to gather lots of advice, in general, from those of have gone before me with this pattern of requirements. Tips could include: How to avoid using timers; how to manage a Windows Service from you GUI and maintain sanity; how to absolutely minimise timers (apparently .NET, even at 4.5.1, simply erases exceptions that are thrown from within Timer event threads); how to survive exceptions that are thrown inside async void methods (apparently these burn the house down).
Then anything else you might recommend, besides barrels of alcohol.
PS: Oh yes, I have Polling Timer #3 as well, to monitor the status of the Host, to disable the GUI trying to communicate with it.
No object is so beautiful that, under certain conditions, it will not look ugly. - Oscar Wilde
modified 15-Mar-15 3:37am.
|
|
|
|
|
Brady Kelly wrote: Polling Timer #1
Replace the timer with a dedicated low-priority thread that loops with a long sleep. When creating a thread, always have a try-catch in the executing code that at least writes the ex.ToString() to the debugger.
Brady Kelly wrote: Also, in the central/default view of the GUI, is the DataGrid that
displays the contents the logging table (Polling Time #2),
If you are watching processes you own, then you could opt to have those processes not only log to a table, but simultaneous update a memory-mapped file. Updating from there whenever there's a change might be a bit faster. You'd also want to broadcast some event whenever you do such an update - the display-app need not poll if it can wait for such an event.
Aight, forget the memory-mapped file; your display-app could be updated over TCP/IP whenever there is something to report.
Brady Kelly wrote: Then anything else you might recommend
Try and catch in every thread, and give each thread a decent name. Helps in debugging
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Thanks Eddy, all good looking stuff, but what do you mean by "your display-app could be updated over TCP/IP"? I can add a callback to the WCF, but the WCF calls code all over town that logs stuff. It would take some work to make the WCF code aware whenever any one of my libraries logs something.
Just BTW, the logging all goes through NLog. That has something like a `MemoryTarget` somewhere, which does raise an event, but then I have to use one logger in all my library code, and have that injected from a core instance in the WCF code itself. Not a train smash, but I'll have to do some Unity refresher reading, and just hold thumbs I can get that working without introducing more bugs.
No object is so beautiful that, under certain conditions, it will not look ugly. - Oscar Wilde
|
|
|
|
|
Brady Kelly wrote: what do you mean by "your display-app could be updated over TCP/IP"? I can add a
callback to the WCF, but the WCF calls code all over town that logs stuff.
I don't know WCF, but I'm familiar with remote debugging. It's essentially a OutputDebugString over the network.
Brady Kelly wrote: That has something like a `MemoryTarget` somewhere, which does raise an event,
but then I have to use one logger in all my library code, and have that injected
from a core instance in the WCF code itself.
..here I don't know what a core instance is. Do me a favor, write an article on the code once it works
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
I've decided to rather stick with a timer for now, because there is a massive amount of logging going on here, and with a timer I can more easily ignore it if I prefer, instead of getting too wrapped in with something that only occasionally needs to be observed real time.
The mysterious "core instance" is just a bad term I used to describe the uncertainty I had over whether it should be a singleton, or a new instance for each injectee, but made by a factory that is a singleton, or maybe just conjured up by Unity or something.
There are so many blog rants paired with educational articles built up around this project it's not funny. I started late today (writing a blog, that is) but won't easily be able to stop. Just let it flow. 
No object is so beautiful that, under certain conditions, it will not look ugly. - Oscar Wilde
|
|
|
|
|
Brady Kelly wrote: The mysterious "core instance" is just a bad term I used to describe the
uncertainty I had over whether it should be a singleton, or a new instance for
each injectee, but made by a factory that is a singleton, or maybe just conjured
up by Unity or something.
"some object" 
Brady Kelly wrote: There are so many blog rants paired with educational articles built up around
this project it's not funny.
Often tied to a platform, specific logger, or the one example on how to inject a logger.
Brady Kelly wrote: I started late today
You're not using Worpress, right? 
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
