|
|
|
I am glad to have helped although you did most of it yourself.
Andy
|
|
|
|
|
I have following error in window service same code is working in window Application
"QueryInterface for interface SQLXMLBULKLOADLib.ISQLXMLBulkLoad failed."
Dim objbl As SQLXMLBulkLoad3
objbl = New SQLXMLBulkLoad3
objbl.ConnectionString = "Provider=SQLOLEDB.1;Data Source=pcDB;Initial Catalog=webdb;User ID=sa;pwd=sa"
objbl.ErrorLogFile = "c:\error.log"
objbl.BulkLoad = True
objbl.KeepIdentity = False
objbl.CheckConstraints = False
objbl.Transaction = False
objbl.Execute("c:\Items.XSD", "C:\Items.xml")
Thanks
Hardik Panchal
|
|
|
|
|
Don't cross post in multiple forums. It's considered very rude to "spam" the forums and makes it quite difficult for multiple people to collaborate on an answer.
|
|
|
|
|
hi all,
installation failed when i tried to install .net 2005 on windows 2003 server with sp1
Any one please help me
thanks and regards
sumanth
this is sumanth, completed m.c.a from india.
|
|
|
|
|
Would you care to tell us what the error message is?? Or should we just guess at the 1,000 or so possible causes for failure...
|
|
|
|
|
Dave Kreskowiak wrote: Or should we just guess at the 1,000 or so possible causes for failure...
I suspect that it's a PEBKAC failure.
|
|
|
|
|
Pete O`Hanlon wrote: I suspect that it's a PEBKAC failure.
I had to Google that one! I normally call it a short between the keyboard and ground.
|
|
|
|
|
Dave Kreskowiak wrote: I normally call it a short between the keyboard and ground
I like that.
|
|
|
|
|
I normally use EBKAC or an ID10T error, but that one only really works when you say it (ID ten T).
|
|
|
|
|
Hi,
I am having the handle to a combo box's dropdown list control which i have grabed by subclassing and overriding the "WNDProc" to receive window message. is there any way by which i can know what is the real object behind this handle.So if it is list control can i assign it to a .Net list control and start using that list control in .Net. i tried control.FromHandle.. Listbox.Fromhandle and and some methods inside the marshal class in .Net
so can you please help me getting the real control behind this handle
|
|
|
|
|
It doesn't work that way. In most cases, you cannot simply slap a .NET controls over a window's handle and treat that handle like a control. Not every control has an unmanaged control sitting behind it.
|
|
|
|
|
First of all Thanks very much for your reply..
and about the scenario.....
Hmmm .. that i know.. in my scenario i am having the handle to the dropdown area (control) of a combobox.
so i want to know whether we can assign/create a list control from this handle. so that i can treat it is a list control and add a control in it or do whatever accoding to the project requirement
|
|
|
|
|
I am having a hard time understanding how default system fonts are obtained in .NET. Specifically, I need to internationalize an app, and I need to be able to specify the font for various controls. What I want is something like the the old GDI call GetStockObject to return GUI font, system font, fixed width font etc. Can someone point me in the right direction?
|
|
|
|
|
Hi
I have some processing in a thread and want to fire some events into the GUI-thread. Kind of like BackgroundWorker.ReportProgress except that I will not be using the BackgroundWorker, but my own thread .
Anyone got any idea how to add some execution to the GUI-thread's event queue?
|
|
|
|
|
Sure, any Control that got created by the GUI thread (thats almost any Control!)
will let you execute stuff on that thread by calling myControl.Invoke
(or BeginInvoke).
Thats how one is supposed to let other threads manipulate said Control in the
first place.
|
|
|
|
|
But what if I dont have any Control to invoke it on? I am making a small library for my own projects, and I want to seperate the processing from the GUI. The processing does not know what components exists and just fire events (that are suppose to happen on the GUI-thread) without knowing what will happen next.
|
|
|
|
|
Aha, I see two possible ways to solve that:
1.
the official way: if your library is independent of the GUI, then it should
not be interested in the GUI thread either. If it needs something done by the app
it should use delegates/events to get the app's attention so it can process
the event. If (part of) the app's reaction needs to run on the GUI thread, then
that's the app's responsibility, so it must organize the InvokeRequired/Invoke stuff.
2.
a hack: create a GUI Control in your app, and pass it on to your library
(maybe thru a Property, possibly a static one). Now your library can use
Invoke itself. You should describe this behavior in your library's documentation
though, since now, even when called from a background thread, the library can load
the GUI thread and harm the resposiveness of the app that uses the library.
|
|
|
|
|
How about the ComponentModel?
I just looked into the Mono sourcecode for BackgroundWorker, and they heavily use the ComponentModel with AsyncOperation.Post and BeginInvoke()
Allthough I am not quite sure how it works, it looks like it could solve my problems.
|
|
|
|
|
I am not familiar with AsyncOperation class; looks promising tho.
BTW: this article[^] just popped up on the home page; it may interest you.
|
|
|
|
|
That was JUST what I was looking for. Cheers!!
|
|
|
|
|
Glad I (or rather CodeProject) could help...
|
|
|
|
|
Hi,
I've been using .NET 2.0 for almost 2 years now. I want to have a look at 3.5, is it worth while looking at it now? Beta 1 is out, does any one know when the Beta 2 will be out?
I want to get started on .NET 3.5, but I heard rumours that Beta 1 is full of errors.
Regards
ma se
|
|
|
|
|
First off, I would say decide which version you want to start learning, either v3.0 or v3.5.
The .NET Framework v3.0 is out now while v3.5 won't be released until the end of this year (or possibly the beginning of next year). That being said, both v3.0 and v3.5 have the v2.0 runtime (CLR) at their core. The differences are in the extra "bits" that have been added.
The .NET Framework v3.0 added WPF, WCF, WF, and CardSpace to the v2.0 Framework while v3.5 adds LINQ and some other bits to the v3.0 Framework.
By learning what is available in v3.5 of the Framework, you will also be learning what is in v3.0 of the Framework.
-----------------------------
In just two days, tomorrow will be yesterday.
|
|
|
|