Friday, March 20, 2020
All About Serializing in Visual Basic
All About Serializing in Visual Basic Serialization is the process of converting an object into a linear sequence of bytes called a byte stream. Deserialization just reverses the process. But why would you want to convert an object into a byte stream? The main reason is so you can move the object around. Consider the possibilities. Since everything is an object in .NET, you can serialize anything and save it to a file. So you could serialize pictures, data files, the current state of a program module (state is like a snapshot of your program at a point in time so you could temporarily suspend execution and start again later) ... whatever you need to do. You can also store these objects on disk in files, send them over the web, pass them to a different program, keep a backup copy for safety or security. The possibilities are quite literally endless. Thats why serialization is such a key process in .NET and Visual Basic. Below is a section on custom serialization by implementing the ISerializable interface and coding a New and a GetObjectData subroutine. As a first example of serialization, lets do one of the easiest programs, but also one of the most useful: serializing data, and then deserializing data in simple class to and from a file. In this example, the data is not only serialized, but the structure of the data is saved too. The structure here is declared in a module to keep things ... well ... structured. Module SerializeParmsSerializable() Public Class ParmExample   Public Parm1Name As String Parm1 Name   Public Parm1Value As Integer 12345   Public Parm2Name As String   Public Parm2Value As DecimalEnd ClassEnd Module Then, individual values can be saved to a file like this: Imports System.Runtime.Serialization.Formatters.BinaryImports System.IOPublic Class Form1   Private Sub mySerialize_Click( _      ByVal sender As System.Object, _      ByVal e As System.EventArgs) _      Handles mySerialize.Click      Dim ParmData As New ParmExample      ParmData.Parm2Name Parm2 Name      ParmData.Parm2Value 54321.12345      Dim s As New FileStream(ParmInfo, FileMode.Create)      Dim f As New BinaryFormatter      f.Serialize(s, ParmData)      s.Close()   End SubEnd Class And those same values can be retrieved like this: Imports System.Runtime.Serialization.Formatters.BinaryImports System.IOPublic Class Form1   Private Sub myDeserialize_Click( _      ByVal sender As System.Object, _      ByVal e As System.EventArgs) _      Handles myDeserialize.Click      Dim s New FileStream(ParmInfo, FileMode.Open)      Dim f As New BinaryFormatter      Dim RestoredParms As New ParmExample      RestoredParms f.Deserialize(s)      s.Close()      Console.WriteLine(RestoredParms.Parm1Name)      Console.WriteLine(RestoredParms.Parm1Value)      Console.WriteLine(RestoredParms.Parm2Name)      Console.WriteLine(RestoredParms.Parm2Value)   End SubEnd Class A Structure or a collection (such as an ArrayList) rather than a Class could also be serialized to a file this same way. Now that we have gone over the basic serializing process, lets look at the specific details that are part of the process on the next page. One of the first things you should notice about this example is the Serializable() attribute in the Class. Attributes are just more information that you can provide to VB.NET about an object and theyre used for a lot of different things. The attribute in this code tells VB.NET to add extra code so that later on, everything in this class can be serialized. If there are specific items in the Class that you dont want to be serialized, you can use the NonSerialized() attribute to exclude them: NonSerialized() Public Parm3Value As String Whatever In the example, notice is that Serialize and Deserialize are methods of the BinaryFormatter object (f in this example). f.Serialize(s, ParmData) This object takes the FileStream object and the object to be serialized as parameters. Well see that VB.NET offers another object that allows the result to be expressed as XML. And one final note, if your object includes other subordinate objects, theyll be serialized too! But since all objects that are serialized must be marked with the Serializable() attribute, all of these child objects must be marked that way too. Just to be completely clear about what is happening in your program, you might want to display the file named ParmData in Notepad to see what serialized data looks like. (If you followed this code, it should be in the bin.Debug folder in your project.) Since this is a binary file, most of the content isnt readable text, but you should be able to see any strings in your serialized file. Well do an XML version next and you might want to compare the two just to be aware of the difference. Serializing to XML instead of a binary file requires very few changes. XML isnt as fast and cant capture some object information, but its far more flexible. XML can be used by just about any other software technology in the world today. If you want to be sure your file structures dont tie you into Microsoft, this is a good option to look into. Microsoft is emphasizing LINQ to XML to create XML data files in their latest technology but many people still prefer this method. The X in XML stands for eXtensible. In our XML example, were going to use one of those extensions of XML, a technology called SOAP. This used to mean Simple Object Access Protocol but now its just a name. (SOAP has been upgraded so much that the original name doesnt fit that well anymore.) The main thing that we have to change in our subroutines is the declation of the serialization formatter. This has to be changed in both the subroutine that serializes the object and the one that deserializes it again. For the default configuration, this involves three changes to your program. First, you have to add a Reference to the project. Right-click the project and select Add Reference .... Make sure ... System.Runtime.Serialization.Formatters.Soap ... has been added to the project. Then change the two statements in the program that references it. Imports System.Runtime.Serialization.Formatters.SoapDim f As New SoapFormatter This time, if you check out the same ParmData file in Notepad, youll see that the whole thing is in readable XML text such as ... Parm1Name idref-3Parm1 Name/Parm1NameParm1Value12345/Parm1ValueParm2Name idref-4Parm2 Name/Parm2NameParm2Value54321.12345/Parm2Value There is also a lot of additional XML there thats necessary for the SOAP standard in the file as well. If you want to verify what the NonSerialized() attribute does, you can add a variable with that attribute and look at the file to verify that its not included. The example we just coded only serialized the data, but suppose you need to control how the data is serialized. VB.NET can do that too! To accomplish this, you need to get a little deeper into the concept of serialization. VB.NET has a new object to help out here: SerializationInfo. Although you have the ability to code custom serialization behavior, it comes with a cost of extra coding. The basic extra code is shown below. Remember, this class is used instead of the ParmExample class shown in the earlier example. This isnt a complete example. The purpose is to show you the new code that is needed for custom serialization. Imports System.Runtime.SerializationSerializable() _Public Class CustomSerialization   Implements ISerializable   data to be serialized here   Public SerializedVariable as Type   Public Sub New()   default constructor when the class   is created - custom code can be   added here too   End Sub   Public Sub New( _      ByVal info As SerializationInfo, _      ByVal context As StreamingContext)      initialize your program variables from      a serialized data store   End Sub   Public Sub GetObjectData( _      ByVal info As SerializationInfo, _      ByVal context As StreamingContext) _      Implements ISerializable.GetObjectData      update the serialized data store      from program variables   End SubEnd Class The idea is that now you can (and, in fact, you must) do all of the updating and reading of data in the serialized data store in the New and GetObjectData subroutines. You must also include a generic New constructor (no parameter list) because youre implementing an interface. The class will normally have formal properties and methods coded as well ... Generic PropertyPrivate newPropertyValue As StringPublic Property NewProperty() As String   Get      Return newPropertyValue   End Get   Set(ByVal value As String)      newPropertyValue value   End SetEnd Property Generic MethodPublic Sub MyMethod()   method codeEnd Sub The resulting serialized class can create unique values in the file based on the code you supply. For example, a real-estate class might update a the value and address of a house but the class would serialize a calculated market classification as well. The New subroutine will look something like this: Public Sub New( _   ByVal info As SerializationInfo, _   ByVal context As StreamingContext)   initialize your program variables from   a serialized data store   Parm1Name info.GetString(a)   Parm1Value info.GetInt32(b)   New sub continues ... When Deserialize is called on a BinaryFormatter object, this sub is executed and a SerializationInfo object is passed to the New subroutine. New can then do whatever is necessary with the serialized data values. For example ... MsgBox(This is Parm1Value Times Pi: _   (Parm1Value * Math.PI).ToString) The reverse happens when Serialize is called, but the BinaryFormatter object calls GetObjectData instead. Public Sub GetObjectData( _   ByVal info As SerializationInfo, _   ByVal context As StreamingContext) _   Implements ISerializable.GetObjectData   update the serialized data store   from program variables   If Parm2Name Test Then      info.AddValue(a, This is a test.)   Else      info.AddValue(a, No test this time.)   End If   info.AddValue(b, 2) Notice that the data is added to the serialized file as name/value pairs. A lot of the web pages Ive found in writing this article dont seem to have actual working code. One wonders whether the author actually executed any code before writing the article sometimes.
Wednesday, March 4, 2020
Filling Vacancies in the US Senate
Filling Vacancies in the US Senate Senate seats become vacant for a variety of reasons the Senator dies in office, resigns in disgrace or resigns to assume another position, usually an elected or appointed government position.What happens when a Senator dies in office or resigns? How is the replacement handled?Procedures for electing Senators are outlined in Article I, Section 3 of the U.S. Constitution, as later amended by paragraph 2 of the Seventeenth (17th) Amendment. Ratified in 1913, the 17th Amendment not only changed how Senators are to be elected (direct election by popular vote) but it also outlined how Senate vacancies are to be filled: When vacancies happen in the representation of any State in the Senate, the executive authority of such State shall issue writs of election to fill such vacancies: Provided, That the legislature of any State may empower the executive thereof to make temporary appointments until the people fill the vacancies by election as the legislature may direct. What Does This Mean in Practice? The U.S. Constitution grants the state legislatures the power to determine how U.S. Senators are to be replaced, including empowering the chief executive (the governor) to make these appointments.Some states require a special election to fill a vacancy. A few states require the governor to appoint a replacement of the same political party as the previous incumbent. Typically, a replacement holds office until the next scheduled statewide election.From the Congressional Research Service: Prevailing practice is for state governors to fill Senate vacancies by appointment, with the appointee serving until a special election has been held, at which time the appointment expires immediately. In the event a seat becomes vacant between the time of a general election and the expiration of the term, however, the appointee usually serves the balance of the term, until the next regularly scheduled general election. This practice originated with the constitutional provision that applied prior to the popular election of senators, under which governors were directed to make temporary appointments when state legislatures were in recess. It was intended to ensure continuity in a state’s Senate representation during the lengthy intervals between state legislative sessions. Exceptions or Where Governors Do Not Have Unlimited Powers: Alaska, Oregon, and Wisconsin do not allow the governor to make interim appointments; state laws require a special election to fill any Senate vacancy. Oklahoma also requires that Senate vacancies be filled by special elections, with an exception. If the vacancy occurs after March 1 of any even-numbered year and the term expires the following year, no special election is held; rather, the governor is required to appoint the candidate elected in the regular general election to fill the unexpired term. Arizona and Hawaii require the governor to fill Senate vacancies with a person affiliated with the same political party as the previous incumbent. Utah and Wyoming require the governor to select an interim senator from a list of three candidates proposed by the state central committee of the political party with which the previous incumbent was affiliated. In the event of a Senator’s death, his or her staff continue to be compensated for a period not exceeding 60 days (unless the Senate Committee on Rules and Administration determines that more time is needed to complete the closing of the office), performing duties under the direction of the Secretary of the Senate.
Subscribe to:
Comments (Atom)