I have a base class ("MyBaseClass") in a project called "BaseFramework" which is included in several solutions within the company. There are several derived class's in various projects throughout the company that inherit from "MyBaseClass". If I then create a List and add derived class's to it, it will not serialize. I realise that if I were attempting to serialize this list, and the base class and derived class were in the same project, I could simply apply the "XmlInclude" attribute to the base class and include all of the derived class's. This is however not possible across projects, because that would require a circular dependency.
I've been using XML serialization for a while, and today I realized something really odd. If I have a new line right after a "dot" (.), when i deserialize, I lose the dot. Has anyone ever had this happen to them? The following is my serialization code:
I have two experimental web services. One is an asmx contained within a .net web application. The other is a WCF service library being invoked from the web application.The asmx basically does everything I need, but I think WCF would be better, except that it doesn't do anything as I would expect after fiddling with the asmx service.For example, the same method behaves differently in each:
' ASMX <WebMethod(BufferResponse:=True, EnableSession:=False)> Function Test(aObject as Object) as Object ' object will have been successfully serializaed into a dictionary
I knew VB.net is very weird when talking about shadows and overloads, but this this I'm completely baffled.I'm working with a model similar to the following one. Parent class:
Public Class Base Function F() As String Return "F() in Base Class" End Function
I'm using the standard code for form drop shadows that creates an effect identical to that of XP's, but you will notice in Windows 7 that the shadows are much larger, are not visible only on the right & bottom sides of the form (example: [URL])
Here's the code I'm currently using:
Private Const CS_DROPSHADOW As Integer = &H20000
Protected Overrides ReadOnly Property CreateParams() As System.Windows.Forms.CreateParams
[CODE]...
Is there a way to expand the shadow to resemble Windows 7 more?
Currently I'm using the standard code for form drop shadows that creates an effect identical to that of XP's, but you will notice in Windows 7 that the shadows are much larger, are not visible only on the right & bottom sides of the form (example: [URL]Here's the code I'm currently using:
Private Const CS_DROPSHADOW As Integer = &H20000 Protected Overrides ReadOnly Property CreateParams() As System.Windows.Forms.CreateParams Get Dim cp As CreateParams = MyBase.CreateParams
[code]....
Is there a way to expand the shadow to resemble Windows 7 more?
when we have a method of a derived class implementing a method of an interface which is already implemented in the base class, the compiler throws a warning (by default). when i see a warning i will try to erase it and the only way to erase this warning is to mess with the settings of the compiler hence i hope that there is a way to declare "how" a method implements an interface's method. by this i meant that we should be able to declare overridable, overrides and shadows for the implements keyword. hence if we declare overridable-implement for a method of a base class implementing an interface's method, the compiler should give no warnings when we override this implementation (re-implementing in a derived class). Similarly, if the method of the base class implementing an itnerface's method was not declared as ovveridable-implement, the derived class should be able to Shadow the implementation example code which flags unnecessary warning:
Warning1property 'Events' shadows an overloadable member declared in the base class 'MarshalByValueComponent'. If you want to overload the base method, this method must be declared 'Overloads'.
I've wanted to know the answer to this question for a long time but I never really took the time to ask anyone. My question is, why do rounded edges or drop shadows of transparent form layouts turn white. Take a look at the following image to know what I'm talking about.
I placed this checkbox named owner on my form. When i build the project i got the error as Quote: 'owner' conflicts with property 'owner' in the base class 'Form' and should be declared 'Shadows'
I am converting an application from vb.net 2003 to 2005. I got the following warning and need help how to resolve it. withEvents variable 'PreviousPage' conflicts with property 'PreviousPage' in the base class 'Page' and should be declared 'Shadows'
Yesterday I started my first DLL project which is for ArabicMessageBox that will allow arabic programmers to display there message in totally Arabic message.My project contain one Form only, and the basic code that I use is:
Public Overridable Function Show(ByVal APrompt As String) As MsgBoxResult mLoad(APrompt, MsgBoxStyle.OkOnly, "") Me.ShowDialog()
Why is XMLSession.FileList.Count always 0. I hypothesize it has something to do with the declaration above it but I am not sure what is wrong with it. Maybe it can't accept a path, if not, how can I do it?
I've been serialising and deserialising .net objects using the XmlSerializer class without problem, however we now need somebody else to look at that data to perform some analysis on it.In order to help with that we've produced an XSD based on our class like so:
Bizarly, the XML produced does not adhere to the XSD generated from the same class.My question then is, is there a way of telling the XmlSerializer to serialize the object based on a given XSD? As an aside, I've looked at other ways of fixing this: I've tried re-generating the classes from the generated XSD - this seemed to have the same problem.
I have a MRU list that keeps on clearing when I close my application. In order to keep this information, I am trying to serialize it to an xml file, however, I can't figure out how to get the list written to this xml file.
Class <Xml.Serialization.XmlRoot(ElementName:="Class_mrulist")> _ Public Class MRULIST
I am attempting to solve the well known problem of automatically generated serialization assemblies in VS 2010, both VB.NET and C#. The "Generate Serialization Assemblies" option in project settings does nothing for non-web projects (see [URL]). Thus the calls to serializers generate file i/o exceptions that are very unfortunate, and for which there is no cure. The method suggested above does not appear to work with VS2010 and SGEN still runs with /proxytypes enabled.
DataContract XML serialization and XML attributes which is most interesting I have attempted to directly convert it to VB.NET, but it does not seem to give me the right results. All I get is the root element with no attributes:
<ServiceContract()> <AspNetCompatibilityRequirements(RequirementsMode:=AspNetCompatibilityRequirementsMode.Allowed)> <ServiceBehavior(InstanceContextMode:=InstanceContextMode.PerCall)> Public Class Service1
I am creating a new windows program and I have used XML serialization to save the contents of my text boxes but when I try to open that file in the new application, no data is transferred. The code acts like it does everything fine and does not give me any errors, it just doesn't input the text back into the program.
what the relation between Serialization and encrypting files, i wanna know that and i wanna a lessons for serialization and i want to ask about this code in VB6 if we can convert it to VB.net 2008
Dim a As String * 10 Dim b As String * 10 Dim c As String * 10
I am new at this. Im trying to serialize a panel and its contents in vb. The controls are added at runtime. I have tried adding to a arraylist but it didnt work
I've been cloning my objects using serialization for awhile, and typically its been quick, at least for my purposes. After a series of updates to these objects, however, now the serialization process is much slower. Trial-and-error has so far failed to pinpoint the cause. Some of the added elements to my object are:
1.binding lists
2. an inherited dictionary class
3. more internal references (the object is actually group of nested objects, and these internal objects have more references to each other than before)
I have been careful to avoid/eliminate references to external elements when cloning, as that can lead to a cascade of extra cloning. So I think the problem is with the object structure itself. This is my serialization routine:
Friend Function CloneObj(ByVal obj As Object) As Object If Not obj.GetType.IsSerializable Then Throw New Exception("Object not serializable") Dim bf As New System.Runtime.Serialization.Formatters.Binary.BinaryFormatter
I tryed using serialization I might be using the wrong thing though what im trying to do is to serialize a class to a .bin file and then use it from another application, is there a way to change the specification of the binary formater this way it works in two different Vb.NET projectS??