Any progress?

Your question belongs in the C++ Forum, not C#. If your trying to use the C# .DLL in Mnaged C++, it's a question for the Managed C++ Forum. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

This is basic. Create another assembly that defines the type. Both the client and server project depend on this assembly and use the type defined in that shared assembly. As far as fixing the version number, go to your AssemblyInfo.cs file and change the AssemblyVersionAttibute value to something fixed (no asterisk - *). If you use an asterisk, the assembly version is automatically generated based on the documentation for the AssemblyVersionAttribute in the .NET Framework SDK. This is a terrible feature that wasn't meant to be in the .NET Framework originally, or so I hear. .NET assemblies link against versions of other assemblies. Changing the version breaks this linkage, but there are ways to redirect assembly versions. Read Redirecting Assembly Versions[^] in the .NET Framework SDK for more information. Microsoft MVP, Visual C# My Articles

Yes. IIRC, the PKCS12 structure can store more information, but I really haven't worked too much with such types of storage structures. Most references to such structures I see are typically PKCS12, however. Microsoft MVP, Visual C# My Articles

pelos wrote: first I must to create programatacally the database and the tables. My question is what is the best way to do this? Don't forget to add data. Aside from what Dave said I think you may be confusing two aspects of the software development lifecycle. You can manually type the DDL to create your database, tables and insert data into or you can use the visual tools that popular RDBMS provide. The purpose of web services is to allow a tranparent transport protocol regardless of operating system for data flow. Does that make sense? - Nick Parker My Blog | My Articles

By using "blob" as the field's type: http://www.winnetmag.com/SQLServer/Article/ArticleID/20461/SQLServer\_20461.html Even better, just save a reference to the file i.e. save it's path as a string in the database. If you have a file server to store your files on, just have your frontend app copy the images there and then save the path (//FILESERVER/SQLSERVERFILES/file1.jpg) in the database. Although SQL server has better performance serving up images (streamed), if a lot of people start using the app at once, the server might get stuck at just streaming files all the time. By just saving the reference, you place the task of getting the image at the client.

thank you... but i dont know how can i define (with visual studio .Net) a web service that can return two different types. In SUN RPC's I used a union with its discriminator to do this, but there's no union in C#. Can you help me? thanks in advance!

ok. i'll try to do it without CryptoAPI. thank you.

It looks like your stored procedure can be simplified to one select statement: SELECT     EmployeeID, FirstName, LastName, Title FROM     Employees WHERE     (@EmployeeID < 1 or EmpolyeeID = @EmployeeID) and     (@Name = '' or FirstName = @Name) and     (@Title = '' or Title = @Title) ORDER BY     EmployeeID FOR XML AUTO[ My articles and software tools ](http://mysite.verizon.net/XiangYangL/index.htm)

here' s a link to a book I recently bought: http://www.amazon.com/exec/obidos/tg/detail/-/013100851X/102-5507300-8534510?v=glance. Also, check out the secrity articles here on CP, I know Heath Stewart did an article on XML signatures/licencing

Hi 1.Register your component under the component services (MTS) 2.Use the export operation in order to create proxy\stub setup file 3.Install the file in the client machine

hello, i think i know what is the problem: I also need a proxy/stub DLL. So, I need to register the proxy/stub DLL on both the client and the server computers. To regisrer the DLL on the server i have done: nmake -f Projectnameps.mk where projectname is the name of my project. This command has built several files, included the Projectname.dll file. Now the problem is that i dont know very well how to register the DLL on the client. I have tried two differents things: 1.- Set up the remote activation using progammatic changes to the client (call CoCreateInstanceEx()instead CoCreateInstance()(),...).But it doesn't run. 2.- Follow the instructions of this article http://www.apostate.com/programming/reg-atl-dcom.html but i dont understand very well the last step: "Use DCOMCNFG to change the execution location of your server from Run application on this computer to Run application on the following computer", and this way to register the DLL sounds a bit rare, doesn´t it?. I am confused... Can you help me? thanks.

Ohh, thanks for your help! ...but now i have got another problem :-O: HRESULT says "interface not compatible" i ve tried it with CoCreateInstanceEx instead CoCreateInstance but the result is the same. Could be the MIDL definition the cause of the problem? Code is something like this: IHelloObj *iHello; // point to teh interface remoto // other variables ans COM inicialitation //mutli_qi strcuture MULTI_QI qi = {&IID_IHelloObj, NULL, S_OK}; //server info COSERVERINFO csi; csi.pwszName = _bstr_t("localhost"); ... hr = CoCreateInstanceEx(CLSID_HelloObj,NULL,CLSCTX_SERVER,&csi, 1,&qi); // here hr and qi.hr are not succeeded if(SUCCEEDED(hr) && SUCCEEDED(qi.hr)) { // get the interface // call to remote methods ... A lot of thanks!!