VBA and C# - C# Discussion Boards

Heath Stewart31-Jul-04 15:02

31-Jul-04 15:02

Can you be a little more specific? Have you even read the .NET Framework SDK for the System.Xml[^] namespace, or are you just looking for someone to do the work for you. You won't find the latter here.

This forum is for asking specific questions, not finding free help. Read the documentation for classes like the XmlTextWriter or the XmlDocument and, if you have questions, ask here.

Microsoft MVP, Visual C#
My Articles

Salman Taseer`31-Jul-04 15:05

Salman Taseer`

31-Jul-04 15:05

thank you sir. actually i wanted a quick hellp coz i have never studied it nut want to use some where in my project.
1. for a little data base
2. dor genrating well formed documents.

any wayz thnx for reply

God bless
byeeee

Rizwan Ahmed

Heath Stewart31-Jul-04 15:10

31-Jul-04 15:10

There's plenty of articles here on CodeProject dealing with such topics - just search or browse the categories. "quick help" won't teach you anything.

Microsoft MVP, Visual C#
My Articles

Salman Taseer`31-Jul-04 15:19

Salman Taseer`

31-Jul-04 15:19

Thnkxx again sir Poke tongue | ;-P

VBA and C#

Anonymous31-Jul-04 7:21

Anonymous

31-Jul-04 7:21

Hi
Now I try to work with C#,but my trouble common and with COM programmin in standart C++. My application had to process an *.xml file through Excel COM. Cause of I use native Excel help for VBA : “VBAXL9.CHM” .But there is any troubles .When C# generate proxy for excel object it not consider about optional argument and cause of I should explicit pass this arguments every time in methods call. In many places into excel help referenced behavior of an methods with parameters by default (optional parameters which omit), but I don’t know what it are.
Where I can learn about definition of this defaults parameters????

Re: VBA and C#

Heath Stewart31-Jul-04 14:59

31-Jul-04 14:59

Use Missing.Value, or something like this for optional parameters:

object missing = Missing.Value;
excel.Save("filename.xls", ref missing, ref missing, ...);

(Note: this is sample code; it won't compile)

The help still applies. Since the RCW (Runtime Callable Wrapper) is generated over the typelib, the types and members are the same (may marshal a little differently; knowing comes from reading and experience).

Read Interoperating with Unmanaged Code[^] in the .NET Framework SDK - especially the parts about COM interop and COM marshaling - for more information.

Microsoft MVP, Visual C#
My Articles

Re: VBA and C#

Anonymous1-Aug-04 3:35

Anonymous

1-Aug-04 3:35

Thank

Re: VBA and C#

Dave Kreskowiak1-Aug-04 4:33

Dave Kreskowiak

1-Aug-04 4:33

And quit crossing posting in so many Forums. It's considered very rude...

RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

NetworkStream/TcpClient

leppie31-Jul-04 6:14

31-Jul-04 6:14

Hi there all

Has anyone experienced the NetworkStream gotten from the TcpClient underload conditions sends out packets in reverse!?

I have done a low-level packet capture of my local port and it confirms what I see at the server. Packets that are queued , tend to get mixed up when the buffer is not full. Seems to send the packets while actually sorting them... any ideas?

^{top secret xacc-ide 0.0.1}

Heath Stewart31-Jul-04 6:22

31-Jul-04 6:22

Set TcpClient.NoDelay to true (default is false). This disables coalescing of packets by sending them immediately instead of storing them until a significant amount of data can be sent. This results in a more chatty protocol, but should eliminate the problems you're having.

Microsoft MVP, Visual C#
My Articles

leppie31-Jul-04 6:28

31-Jul-04 6:28

Heath Stewart wrote:
TcpClient.NoDelay to true

Tried that, and every property I have access too, still the same...

^{top secret xacc-ide 0.0.1}

leppie31-Jul-04 6:33

31-Jul-04 6:33

Other things I have tried (but same results):

- Send ever packet via a threadpool

It only happens when the NetworkStream is buffering (when doing Write in "quick" (still by hand!) succession). Its not the server either, this has been verified by the captured packets, and the fact that an unmamaged client behaves correctly in the same scenario.

^{top secret xacc-ide 0.0.1}

Heath Stewart31-Jul-04 15:12

31-Jul-04 15:12

Out of curiosity (sorry, no clue what might be wrong without digging into lots of IL (and a lot is actually internal implementation in the CLR - I always hate that road block)), why would you try to solve this in a ThreadPool? I would expect that to make it worse (nothing says your queued work items are executed in order).

Microsoft MVP, Visual C#
My Articles

leppie31-Jul-04 21:53

refreshing .dlls after compilation

31-Jul-04 21:53

My initial idea, although I dont think it works like I thought ( Blush | :O

) was to just get a little pause or something, tried some locks too.

Basically I place a Console.Write after the NetworkStream.Write , so I can see it IS being dispatched by me, in a sequencial order, which I have confirmed.

Here is a trimmed version of a packet "dispatch" leaving my port, as captured, by NGSniff and WinPCap, each line refers to a stream.Write action, where the id is generated sequencially, and the data is just entered on the keyboard. This refers to a single packet leaving my network port.

id="msg135" 7
id="msg134" 6
id="msg136" 8
id="msg137" 9

In this case, the order seems random, most other cases the order seems to be in reverse, that would look like:

id="msg137" 9
id="msg136" 8
id="msg135" 7
id="msg134" 6

This can surely not be the real behaviour of the NetworkStream, as for a workaround I would have to add an unessary packet layer that should already be provided on a lower OSI level. Unsure | :~

Thanks for trying to help though Smile | :)

^{top secret xacc-ide 0.0.1}

Cristoff31-Jul-04 2:19

Cristoff

31-Jul-04 2:19

I'm developing components in separate .dlls. Unfortunately I have to manually delete the compiled .dlls so that they are refreshed in the main project each time I change them? Is there any other way (automatic)?

It is the same story with the resources but I know it is an issue with VS.NET. It is quite annoying each time I change a resource I have to remove it and then add it again.

Heath Stewart31-Jul-04 4:52

31-Jul-04 4:52

Remove the assembly references. Right-click on the project that depends on those assemblies, select Add Reference. Click the Project tab and add the projects in your solution that your current project depends on. Now a build dependency is established so that any changes in a dependent project (or their dependents, etc.) will force a recompile and - if necessary - will copy the newly built assembly into the target path for the project that depends on it. This also makes sure that the versions are never incorrect, though you really shouldn't use automatic versioning in larger solutions because versions in .NET are important (they are part of what defines a Type - a difference only in version results in different Types).

If you read the Visual Studio product documentation - or even just explore the IDE - you can find a lot more useful tips.

Microsoft MVP, Visual C#
My Articles

Cristoff31-Jul-04 19:12

Cristoff

31-Jul-04 19:12

Well, all my projects are in the same solution from the start but most of the time, when I change any of the .dlls the newer versions are not copied in the .exe folder. Most of the time this happens only if I delete the bin folder Smile | :)

and execute Build twice.

I have thought about outputting the compiled .dll directly in the main projects bin folder but I haven't tried it yet. Smile | :)

there should be a more logical solution.

Heath Stewart31-Jul-04 19:14

31-Jul-04 19:14

Cristoff wrote:
there should be a more logical solution

There is: as I said, reference your projects in a solution using the Projects tab - not the .NET tab. Trust me - I managed a solution of well over 60 projects as the senior software architect and build master for a very large, N-tier .NET application using VS.NET.

This will set up build dependencies and will update your dependent assemblies for a project that references them (directly and indirectly) in the target path (bin\Debug, bin\Release, etc.). And also as I said before, this is documented in the Visual Studio product documentation.

Microsoft MVP, Visual C#
My Articles

Can i trigger an event to a C# app in a C++ DLL?

Cristoff31-Jul-04 20:37

Cristoff

31-Jul-04 20:37

Thank you,

I have followed your suggestion and I think I have found your proposed solution.

I have been so convinced that adding an assembly reference is all I have to do that I have never thought that Project dependancy is something different.

BTW I have almost given up programming at the end of the last year and I haven't touched a compiler since then but the necessity has made me do it again Smile | :)

Your so helpful to the community! Thank you!

fu031-Jul-04 1:43

fu0

31-Jul-04 1:43

i m writting a C++ Win32 DLL which is called by a C# application.
i want the DLL can trigger an event to the Calling C# app after some operations which might like the Win MSG mechanism: The DLL send a message to the C# app and the C# app handle the msg.

the C# use the EventHandle/EventArgs on this issue.

But can i trigger an event to C# app in a C++ Win32 DLL ?

please help me.

Re: Can i trigger an event to a C# app in a C++ DLL?

Heath Stewart31-Jul-04 5:46