Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / Remoting / June 2004

Tip: Looking for answers? Try searching our database.

Get "not mark as serializable" when passing VB6 Type as a parameter

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
ylangevin - 28 Jun 2004 21:45 GMT
Hi,
 I have a project where I need to separate a VB app from his components that will reside on a separate machine. I've decided to use the .Net remoting to do accomplish this. My solution is to recreate the .net components with the same signature that the vb components and only change the references in my VB app and recompile it. This way, when the vb app creates a new obejct, the .net component is being created instead of the vb component. The .net component then creates a remote call to access the vb code on a remote machine.

When a remote call is done with a vb class, everything works fine, but when the call has a vb public type as a parameter, I always get the "not marked as serializable" error. Does anyone has an idea of what it may be?

thanks

---
Allen Anderson - 29 Jun 2004 15:10 GMT
I believe Sunny correctly answered this in a previous post.

Allen Anderson
http://www.glacialcomponents.com
mailto: allen@put my website base here.com

>Hi,
>  I have a project where I need to separate a VB app from his components that will reside on a separate machine. I've decided to use the .Net remoting to do accomplish this. My solution is to recreate the .net components with the same signature that the vb components and only change the references in my VB app and recompile it. This way, when the vb app creates a new obejct, the .net component is being created instead of the vb component. The .net component then creates a remote call to access the vb code on a remote machine.
[quoted text clipped - 4 lines]
>
>---

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.