Bug 406446. Fix assembly version so that upgrading files works properly. (Windows Only)

This commit is contained in:
Jim Norman 2008-07-08 05:06:16 +00:00
parent 6c561fdcaa
commit d55e7138fc
15 changed files with 183 additions and 183 deletions

View File

@ -48,7 +48,7 @@ using System.Runtime.CompilerServices;
// You can specify all the values or you can default the Revision and Build Numbers
// by using the '*' as shown below:
[assembly: AssemblyVersion("1.6.*")]
[assembly: AssemblyVersion("1.7.*")]
//
// In order to sign your assembly you must specify a key to use. Refer to the

View File

@ -82,6 +82,88 @@
</summary>
</member>
<member name="T:AppModule.InterProcessComm.IClientChannel">
<summary>
</summary>
</member>
<member name="M:AppModule.InterProcessComm.IClientChannel.HandleRequest(System.String)">
<summary>
</summary>
<param name="request"></param>
<returns></returns>
</member>
<member name="M:AppModule.InterProcessComm.IClientChannel.HandleRequest(System.IO.Stream)">
<summary>
</summary>
<param name="request"></param>
<returns></returns>
</member>
<member name="M:AppModule.InterProcessComm.IClientChannel.HandleRequest(System.Object)">
<summary>
</summary>
<param name="request"></param>
<returns></returns>
</member>
<member name="M:AppModule.InterProcessComm.IClientChannel.Create">
<summary>
</summary>
<returns></returns>
</member>
<member name="T:AppModule.InterProcessComm.IChannelManager">
<summary>
Interface, which defines methods for a Channel Manager class.
</summary>
<remarks>
A Channel Manager is responsible for creating and maintaining channels for inter-process communication. The opened channels are meant to be reusable for performance optimization. Each channel needs to procees requests by calling the <see cref="M:AppModule.InterProcessComm.IChannelManager.HandleRequest(System.String)">HandleRequest</see> method of the Channel Manager.
</remarks>
</member>
<member name="M:AppModule.InterProcessComm.IChannelManager.Initialize">
<summary>
Initializes the Channel Manager.
</summary>
</member>
<member name="M:AppModule.InterProcessComm.IChannelManager.Stop">
<summary>
Closes all opened channels and stops the Channel Manager.
</summary>
</member>
<member name="M:AppModule.InterProcessComm.IChannelManager.HandleRequest(System.String)">
<summary>
Handles a request.
</summary>
<remarks>
This method currently caters for text based requests. XML strings can be used in case complex request structures are needed.
</remarks>
<param name="request">The incoming request.</param>
<returns>The resulting response.</returns>
</member>
<member name="M:AppModule.InterProcessComm.IChannelManager.WakeUp">
<summary>
Forces the Channel Manager to exit a sleeping mode and create a new channel.
</summary>
<remarks>
Normally the Channel Manager will create a number of reusable channels, which will handle the incoming reqiests, and go into a sleeping mode. However if the request load is high, the Channel Manager needs to be asked to create additional channels.
</remarks>
</member>
<member name="M:AppModule.InterProcessComm.IChannelManager.RemoveServerChannel(System.Object)">
<summary>
Removes an existing channel.
</summary>
<param name="param">A parameter identifying the channel.</param>
</member>
<member name="P:AppModule.InterProcessComm.IChannelManager.Listen">
<summary>
Indicates whether the Channel Manager is in listening mode.
</summary>
<remarks>
This property is left public so that other classes, like a server channel can start or stop listening based on the Channel Manager mode.
</remarks>
</member>
<member name="T:AppModule.InterProcessComm.InterProcessConnectionState">
<summary>
@ -177,87 +259,5 @@
</summary>
</member>
<member name="T:AppModule.InterProcessComm.IChannelManager">
<summary>
Interface, which defines methods for a Channel Manager class.
</summary>
<remarks>
A Channel Manager is responsible for creating and maintaining channels for inter-process communication. The opened channels are meant to be reusable for performance optimization. Each channel needs to procees requests by calling the <see cref="M:AppModule.InterProcessComm.IChannelManager.HandleRequest(System.String)">HandleRequest</see> method of the Channel Manager.
</remarks>
</member>
<member name="M:AppModule.InterProcessComm.IChannelManager.Initialize">
<summary>
Initializes the Channel Manager.
</summary>
</member>
<member name="M:AppModule.InterProcessComm.IChannelManager.Stop">
<summary>
Closes all opened channels and stops the Channel Manager.
</summary>
</member>
<member name="M:AppModule.InterProcessComm.IChannelManager.HandleRequest(System.String)">
<summary>
Handles a request.
</summary>
<remarks>
This method currently caters for text based requests. XML strings can be used in case complex request structures are needed.
</remarks>
<param name="request">The incoming request.</param>
<returns>The resulting response.</returns>
</member>
<member name="M:AppModule.InterProcessComm.IChannelManager.WakeUp">
<summary>
Forces the Channel Manager to exit a sleeping mode and create a new channel.
</summary>
<remarks>
Normally the Channel Manager will create a number of reusable channels, which will handle the incoming reqiests, and go into a sleeping mode. However if the request load is high, the Channel Manager needs to be asked to create additional channels.
</remarks>
</member>
<member name="M:AppModule.InterProcessComm.IChannelManager.RemoveServerChannel(System.Object)">
<summary>
Removes an existing channel.
</summary>
<param name="param">A parameter identifying the channel.</param>
</member>
<member name="P:AppModule.InterProcessComm.IChannelManager.Listen">
<summary>
Indicates whether the Channel Manager is in listening mode.
</summary>
<remarks>
This property is left public so that other classes, like a server channel can start or stop listening based on the Channel Manager mode.
</remarks>
</member>
<member name="T:AppModule.InterProcessComm.IClientChannel">
<summary>
</summary>
</member>
<member name="M:AppModule.InterProcessComm.IClientChannel.HandleRequest(System.String)">
<summary>
</summary>
<param name="request"></param>
<returns></returns>
</member>
<member name="M:AppModule.InterProcessComm.IClientChannel.HandleRequest(System.IO.Stream)">
<summary>
</summary>
<param name="request"></param>
<returns></returns>
</member>
<member name="M:AppModule.InterProcessComm.IClientChannel.HandleRequest(System.Object)">
<summary>
</summary>
<param name="request"></param>
<returns></returns>
</member>
<member name="M:AppModule.InterProcessComm.IClientChannel.Create">
<summary>
</summary>
<returns></returns>
</member>
</members>
</doc>

View File

@ -48,7 +48,7 @@ using System.Runtime.CompilerServices;
// You can specify all the values or you can default the Revision and Build Numbers
// by using the '*' as shown below:
[assembly: AssemblyVersion("1.6.0.*")]
[assembly: AssemblyVersion("1.7.*")]
//
// In order to sign your assembly you must specify a key to use. Refer to the

View File

@ -185,39 +185,6 @@
Object destructor.
</summary>
</member>
<member name="T:AppModule.NamedPipes.PipeHandle">
<summary>
Holds the operating system native handle and the current state of the pipe connection.
</summary>
</member>
<member name="F:AppModule.NamedPipes.PipeHandle.Handle">
<summary>
The operating system native handle.
</summary>
</member>
<member name="F:AppModule.NamedPipes.PipeHandle.State">
<summary>
The current state of the pipe connection.
</summary>
</member>
<member name="M:AppModule.NamedPipes.PipeHandle.#ctor(System.Int32)">
<summary>
Creates a PipeHandle instance using the passed native handle.
</summary>
<param name="hnd">The native handle.</param>
</member>
<member name="M:AppModule.NamedPipes.PipeHandle.#ctor(System.Int32,AppModule.InterProcessComm.InterProcessConnectionState)">
<summary>
Creates a PipeHandle instance using the provided native handle and state.
</summary>
<param name="hnd">The native handle.</param>
<param name="state">The state of the pipe connection.</param>
</member>
<member name="M:AppModule.NamedPipes.PipeHandle.#ctor">
<summary>
Creates a PipeHandle instance with an invalid native handle.
</summary>
</member>
<member name="T:AppModule.NamedPipes.NamedPipeIOException">
<summary>
This exception is thrown by named pipes communication methods.
@ -243,6 +210,68 @@
<param name="info">The serialization information.</param>
<param name="context">The streaming context.</param>
</member>
<member name="T:AppModule.NamedPipes.ServerPipeConnection">
<summary>
Used by server applications to communicate with client ones by using named pipes.
</summary>
</member>
<member name="M:AppModule.NamedPipes.ServerPipeConnection.Disconnect">
<summary>
Disconnects a client named pipe.
</summary>
<remarks>
When a client named pipe is disconnected, the server one is not closed.
The latter can later be reused by starting to listen again.<br/><br/>
In a message oriented protocol the server will disconnect the client when the
response is sent and all the data is flushed. The same server named pipe
could then be reused by calling the
<see cref="M:AppModule.NamedPipes.ServerPipeConnection.Connect">Connect</see> method.
</remarks>
</member>
<member name="M:AppModule.NamedPipes.ServerPipeConnection.Close">
<summary>
Closes the operating system native handle of the named pipe.
</summary>
</member>
<member name="M:AppModule.NamedPipes.ServerPipeConnection.Connect">
<summary>
Starts listening to client pipe connections.
</summary>
<remarks>
This method will block the program execution until a client pipe attempts
to establish a connection.<br/><br/>
When a client named pipe is disconnected, the server one is not closed.
The latter can later be reused by starting to listen again.<br/><br/>
</remarks>
</member>
<member name="M:AppModule.NamedPipes.ServerPipeConnection.#ctor(System.String,System.UInt32,System.UInt32,System.Int32)">
<summary>
Creates a ServerPipeConnection instance and the underlying operating system handle.
</summary>
<param name="name">The name of the pipe.</param>
<param name="outBuffer">The outbound buffer.</param>
<param name="inBuffer">The inbound buffer.</param>
<param name="maxReadBytes">The maximum bytes to read from clients.</param>
</member>
<member name="M:AppModule.NamedPipes.ServerPipeConnection.#ctor(System.String,System.UInt32,System.UInt32,System.Int32,System.Boolean)">
<summary>
Creates a ServerPipeConnection instance and the underlying operating system handle.
</summary>
<param name="name">The name of the pipe.</param>
<param name="outBuffer">The outbound buffer.</param>
<param name="inBuffer">The inbound buffer.</param>
<param name="secure">Specifies whether the pipe is secure.</param>
<param name="maxReadBytes">The maximum bytes to read from clients.</param>
<remarks>If the <b>secure</b> parameter is true the default security descriptor is used. The ACLs in the default security descriptor for a named pipe grant full control to the LocalSystem account, administrators, and the creator owner. They also grant read access to members of the Everyone group and the anonymous account.
<br/><br/>
If the <b>secure</b> parameter is false the method creates a security descriptor that grants full access to Everyone.
</remarks>
</member>
<member name="M:AppModule.NamedPipes.ServerPipeConnection.Finalize">
<summary>
Object destructor.
</summary>
</member>
<member name="T:AppModule.NamedPipes.ImpersonateNative">
<summary>
This utility class exposes kernel32.dll methods for named pipes communication.
@ -483,66 +512,37 @@
Private constructor.
</summary>
</member>
<member name="T:AppModule.NamedPipes.ServerPipeConnection">
<member name="T:AppModule.NamedPipes.PipeHandle">
<summary>
Used by server applications to communicate with client ones by using named pipes.
Holds the operating system native handle and the current state of the pipe connection.
</summary>
</member>
<member name="M:AppModule.NamedPipes.ServerPipeConnection.Disconnect">
<member name="F:AppModule.NamedPipes.PipeHandle.Handle">
<summary>
Disconnects a client named pipe.
</summary>
<remarks>
When a client named pipe is disconnected, the server one is not closed.
The latter can later be reused by starting to listen again.<br/><br/>
In a message oriented protocol the server will disconnect the client when the
response is sent and all the data is flushed. The same server named pipe
could then be reused by calling the
<see cref="M:AppModule.NamedPipes.ServerPipeConnection.Connect">Connect</see> method.
</remarks>
</member>
<member name="M:AppModule.NamedPipes.ServerPipeConnection.Close">
<summary>
Closes the operating system native handle of the named pipe.
The operating system native handle.
</summary>
</member>
<member name="M:AppModule.NamedPipes.ServerPipeConnection.Connect">
<member name="F:AppModule.NamedPipes.PipeHandle.State">
<summary>
Starts listening to client pipe connections.
The current state of the pipe connection.
</summary>
<remarks>
This method will block the program execution until a client pipe attempts
to establish a connection.<br/><br/>
When a client named pipe is disconnected, the server one is not closed.
The latter can later be reused by starting to listen again.<br/><br/>
</remarks>
</member>
<member name="M:AppModule.NamedPipes.ServerPipeConnection.#ctor(System.String,System.UInt32,System.UInt32,System.Int32)">
<member name="M:AppModule.NamedPipes.PipeHandle.#ctor(System.Int32)">
<summary>
Creates a ServerPipeConnection instance and the underlying operating system handle.
Creates a PipeHandle instance using the passed native handle.
</summary>
<param name="name">The name of the pipe.</param>
<param name="outBuffer">The outbound buffer.</param>
<param name="inBuffer">The inbound buffer.</param>
<param name="maxReadBytes">The maximum bytes to read from clients.</param>
<param name="hnd">The native handle.</param>
</member>
<member name="M:AppModule.NamedPipes.ServerPipeConnection.#ctor(System.String,System.UInt32,System.UInt32,System.Int32,System.Boolean)">
<member name="M:AppModule.NamedPipes.PipeHandle.#ctor(System.Int32,AppModule.InterProcessComm.InterProcessConnectionState)">
<summary>
Creates a ServerPipeConnection instance and the underlying operating system handle.
Creates a PipeHandle instance using the provided native handle and state.
</summary>
<param name="name">The name of the pipe.</param>
<param name="outBuffer">The outbound buffer.</param>
<param name="inBuffer">The inbound buffer.</param>
<param name="secure">Specifies whether the pipe is secure.</param>
<param name="maxReadBytes">The maximum bytes to read from clients.</param>
<remarks>If the <b>secure</b> parameter is true the default security descriptor is used. The ACLs in the default security descriptor for a named pipe grant full control to the LocalSystem account, administrators, and the creator owner. They also grant read access to members of the Everyone group and the anonymous account.
<br/><br/>
If the <b>secure</b> parameter is false the method creates a security descriptor that grants full access to Everyone.
</remarks>
<param name="hnd">The native handle.</param>
<param name="state">The state of the pipe connection.</param>
</member>
<member name="M:AppModule.NamedPipes.ServerPipeConnection.Finalize">
<member name="M:AppModule.NamedPipes.PipeHandle.#ctor">
<summary>
Object destructor.
Creates a PipeHandle instance with an invalid native handle.
</summary>
</member>
<member name="T:AppModule.NamedPipes.NamedPipeNative">
@ -958,16 +958,6 @@
This class is used as a dummy parameter only.
</summary>
</member>
<member name="T:AppModule.NamedPipes.ImpersonateWrapper">
<summary>
A utility class that exposes named pipes operations.
</summary>
<remarks>
This class uses the exposed exposed kernel32.dll methods by the
<see cref="T:AppModule.NamedPipes.NamedPipeNative">NamedPipeNative</see> class
to provided controlled named pipe functionality.
</remarks>
</member>
<member name="T:AppModule.NamedPipes.NamedPipeWrapper">
<summary>
A utility class that exposes named pipes operations.
@ -1156,5 +1146,15 @@
Private constructor.
</summary>
</member>
<member name="T:AppModule.NamedPipes.ImpersonateWrapper">
<summary>
A utility class that exposes named pipes operations.
</summary>
<remarks>
This class uses the exposed exposed kernel32.dll methods by the
<see cref="T:AppModule.NamedPipes.NamedPipeNative">NamedPipeNative</see> class
to provided controlled named pipe functionality.
</remarks>
</member>
</members>
</doc>

View File

@ -47,7 +47,7 @@ using System.Runtime.CompilerServices;
// You can specify all the values or you can default the Revision and Build Numbers
// by using the '*' as shown below:
[assembly: AssemblyVersion("1.6.0.*")]
[assembly: AssemblyVersion("1.7.*")]
//
// In order to sign your assembly you must specify a key to use. Refer to the

View File

@ -48,7 +48,7 @@ using System.Runtime.CompilerServices;
// You can specify all the values or you can default the Revision and Build Numbers
// by using the '*' as shown below:
[assembly: AssemblyVersion("1.6.*")]
[assembly: AssemblyVersion("1.7.*")]
//
// In order to sign your assembly you must specify a key to use. Refer to the

View File

@ -29,5 +29,5 @@ using System.Runtime.InteropServices;
// Build Number
// Revision
//
[assembly: AssemblyVersion("1.0.0.0")]
[assembly: AssemblyFileVersion("1.0.0.0")]
[assembly: AssemblyVersion("1.7.*")]
[assembly: AssemblyFileVersion("1.7.*")]

View File

@ -49,7 +49,7 @@ using System.Runtime.CompilerServices;
// You can specify all the values or you can default the Revision and Build Numbers
// by using the '*' as shown below:
[assembly: AssemblyVersion("1.6.*")]
[assembly: AssemblyVersion("1.7.*")]
//
// In order to sign your assembly you must specify a key to use. Refer to the

View File

@ -48,7 +48,7 @@ using System.Runtime.CompilerServices;
// You can specify all the values or you can default the Revision and Build Numbers
// by using the '*' as shown below:
[assembly: AssemblyVersion("1.6.*")]
[assembly: AssemblyVersion("1.7.*")]
//
// In order to sign your assembly you must specify a key to use. Refer to the

View File

@ -321,14 +321,14 @@
{
"Name" = "8:Microsoft Visual Studio"
"ProductName" = "8:CASA"
"ProductCode" = "8:{82D754E5-AC82-48BC-B7AF-FAC9DBCBA9BF}"
"PackageCode" = "8:{804966BB-71F8-4568-A716-664AD4C48308}"
"ProductCode" = "8:{334EA151-EE96-456E-AE0B-26C877E2D082}"
"PackageCode" = "8:{9DB7BF48-CCF3-45A4-93AF-C7F7BA768048}"
"UpgradeCode" = "8:{DFD8B8A0-EA51-4202-831C-7CD2B90A63AE}"
"RestartWWWService" = "11:FALSE"
"RemovePreviousVersions" = "11:TRUE"
"DetectNewerInstalledVersion" = "11:TRUE"
"InstallAllUsers" = "11:TRUE"
"ProductVersion" = "8:1.7.1041"
"ProductVersion" = "8:1.7.1554"
"Manufacturer" = "8:Novell"
"ARPHELPTELEPHONE" = "8:"
"ARPHELPLINK" = "8:"

View File

@ -48,7 +48,7 @@ using System.Runtime.CompilerServices;
// You can specify all the values or you can default the Revision and Build Numbers
// by using the '*' as shown below:
[assembly: AssemblyVersion("1.6.*")]
[assembly: AssemblyVersion("1.7.*")]
//
// In order to sign your assembly you must specify a key to use. Refer to the

View File

@ -48,7 +48,7 @@ using System.Runtime.CompilerServices;
// You can specify all the values or you can default the Revision and Build Numbers
// by using the '*' as shown below:
[assembly: AssemblyVersion("1.6.*")]
[assembly: AssemblyVersion("1.7.*")]
//
// In order to sign your assembly you must specify a key to use. Refer to the

View File

@ -48,7 +48,7 @@ using System.Runtime.CompilerServices;
// You can specify all the values or you can default the Revision and Build Numbers
// by using the '*' as shown below:
[assembly: AssemblyVersion("1.0.*")]
[assembly: AssemblyVersion("1.7.*")]
//
// In order to sign your assembly you must specify a key to use. Refer to the