Blog Home  Home Feed your aggregator (RSS 2.0)  
Software Code Help blogs
newtelligence powered
 
 Thursday, June 12, 2008

To shrink your virtual PC virtaul hard disk, There are following setup given below :

1. Turn On your virtual PC machine.
2. Clean up your drive by Recycle Bin and other temporary file.
3. On your local system there is  a file named virtual disk precompactor.iso (it should be in c:\program files\microsoft virtual pc\virtual machine additions).Just click on CD Menu on your top VPC Machine and specify the path of ISO file and capture the ISO image . This will start the precompactor program which zeros out unused space.


then this start for compacting your VPC virtual hard disk.

Thursday, June 12, 2008 7:25:23 AM (GMT Standard Time, UTC+00:00)  #    Comments [0]   C#  | 
 Wednesday, June 11, 2008

To create your setup file in silent mode.

First you create a Setup.iss file using this command on command prompt

C:\Setup Path\Setup -r

 

After running this setup.iss file is created in your Windows Folder.

 

Copy this file and paste where your setup file exists.

 

After this, Create a batch file with this command.

--------------------------------

 

echo Start Installing YOur Setup

 

setup -s

 

--------------------------------

 

This batch file automatically take setup.iss file from same folder where this batch file is running.

 

After running this batch file, there is setup.log file is created. Check this file.

 

Using "Silent Installation" with InstallShield there is only one chance to analyze the reason for cancelling an Installation.

 

Locate the File setup.log, usually in <WindowsFolder> or batch file folder, jump to the Paragraph  [ResponseResult]

 

ResultCode contains a Value 

 

0

Success

-1

General error

-2

Invalid mode

-3

Required data not found in setup.iss

-4

Not enough memory available

-5

File does not exist (setup.iss -- try -f1.\setup.iss )

-6

Cannot write to the response file

-7

Unable to write to the log file

-8

Invalid path to the InstallShield Silent response file

-9

 Not a valid list type (string or number)

-10

Data type is invalid

-11

Unknown error during setup

-12

Dialogs are out of order (Version prior 6, evtl. it is -3))

-51

Cannot create the specified folder

-52

Cannot access the specified file or folder

-53

Invalid option selected

 There are below parameter details which we can use with Setup.exe file.

 

Parameter

Description

-d

Runs setup in debug mode. The -d switch also includes a <pathonly> option for specifying the path of the Setup.rul file. For more information, refer to the Visual Debugger help file.

-f<path\CompiledScript>

Specifies an alternate compiled script. Unless the compiled script (.ins file) also resides in the same directory as that of Setup.exe, the full path to the compiled script must be specified. _setup.dll must also reside in the same directory as your .ins file. For example, setup -ftest.ins will launch setup using Test.ins instead of Setup.ins.

-f1<path\ResponseFile>

Specifies an alternate location and name of the response file (.iss file). If this option is used when running InstallShield Silent, the response file is read from the folder/file specified by<path\ResponseFile>. If this option is used along with the -r option, the response file is written to the folder/file specified by<path\ResponseFile>. If an alternate compiled script is specified using the -f switch, the -f1 switch entry must follow the -f switch entry.

-f2<path\LogFile>

Specifies an alternate location and name of the log file created by InstallShield Silent. By default, Setup.log log file is created and stored in the same directory as that of Setup.ins. If an alternate compiled script is specified using the -f switch, the -f2 switch entry must follow the -f switch entry.

-m<filename>

Causes Setup.exe to generate a Management Information Format (.mif) file automatically at the end of the setup. Do not include a path - the .mif file is always placed in the Windows folder. <filename> is optional. If you do not specify a filename, the resulting file will be called Status.mif.

-m1<serial number>

Tells setup to place the indicated serial number in the created .mif file.

-m2<locale string>

Tells setup to place the indicated locale in the .mif file. English (ENU) is the default; refer to Microsoft documentation for a complete listing of locale strings.

-r

Causes Setup.exe automatically to generate a silent setup file (.iss file), which is a record of the setup input, in the Windows folder.

-s

Runs InstallShield Silent to execute a silent setup.

-SMS

Prevents a network connection and Setup.exe from closing before the setup is complete. This switch works with setups originating from a Windows NT server over a network. Please note that SMS must be uppercase; this is a case-sensitive switch.

-z

Prevents Setup.exe from checking the available memory during initialization. This switch is necessary when running a setup on a machine with more than 256 MB of memory; if it is not used, Setup.exe reports insufficient memory and exits.

 

Wednesday, June 11, 2008 9:43:34 AM (GMT Standard Time, UTC+00:00)  #    Comments [0]   InstallShield  | 

The setting the MaxStringContentLength of the XmlReader used by the WS Binding.

At the server side, I have the following in the Web.config:

 


 

<system.serviceModel>

<services>

<service name="Service.ServiceClass" behaviorConfiguration="Service.ServiceClassBehavior">

<endpoint address="" binding="basicHttpBinding" contract="Service.Interface.DataService" bindingConfiguration="BasicHttpBinding">

</endpoint>

<endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange"/>

</service>

</services>

<behaviors>

<serviceBehaviors>

<behavior name="Service.ServiceClassBehavior">

<!-- To avoid disclosing metadata information, set the value below to false and remove the metadata endpoint above before deployment -->

<serviceMetadata httpGetEnabled="true"/>

<!-- To receive exception details in faults for debugging purposes, set the value below to true. Set to false before deployment to avoid disclosing exception information -->

<serviceDebug includeExceptionDetailInFaults="true"/>

</behavior>

</serviceBehaviors>

</behaviors>

<bindings>

<basicHttpBinding>

<binding name="BasicHttpBinding" closeTimeout="00:01:00"

openTimeout="00:01:00" receiveTimeout="00:10:00" sendTimeout="00:01:00"

allowCookies="false" bypassProxyOnLocal="false" hostNameComparisonMode="StrongWildcard"

maxBufferSize="2147483647" maxBufferPoolSize="2147483647" maxReceivedMessageSize="2147483647"

messageEncoding="Text" textEncoding="utf-8" transferMode="Buffered"

useDefaultWebProxy="true">

<readerQuotas maxDepth="2147483647" maxStringContentLength="2147483647" maxArrayLength="2147483647"

maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647" />

<security mode="None">

<transport clientCredentialType="None" proxyCredentialType="None"

realm="" />

<message clientCredentialType="UserName" algorithmSuite="Default" />

</security>

</binding>

</basicHttpBinding>

</bindings>

</system.serviceModel>

After doing this setting in web config on server side, my problem of 8192 ContentString size problem is sorted out.

Wednesday, June 11, 2008 5:05:49 AM (GMT Standard Time, UTC+00:00)  #    Comments [0]   C#  | 
 Monday, June 09, 2008

This code is used for Serialize a object and get object details in XMLDocument.

//Namespace using for Serilization

using System.Xml.Serialization;
using System.IO;

Code using for serialize object

 

//Serialize and Deserialize Objects

XmlSerializer objSerializer;

//Creating Stream whose backing stores in memory.

MemoryStream objMemStream = new MemoryStream();

//Xml Serialization

objSerializer = new XmlSerializer(typeof(SendDetailRequest));

//Store object data into Memory Stream object

objSerializer.Serialize(objMemStream, sendDetailRequest);

//Create XML document for storing respnose

System.Xml.XmlDocument responseXML = new System.Xml.XmlDocument();

responseXML.LoadXml(System.Text.UTF8Encoding.Default.GetString(objMemStream.ToArray()));

//Save the Serialize response

responseXML.Save("C://Response.xml");

Monday, June 09, 2008 4:03:45 AM (GMT Standard Time, UTC+00:00)  #    Comments [0]   C#  | 

This script is used for storing database using SQL Script.

RESTORE DATABASE [Data] FROM DISK = N 'Database Path' WITH FILE = 1,

MOVE N'Data' TO N'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\Data_Data.mdf',

MOVE N'Data_log' TO N'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\Data_Log.ldf', NOUNLOAD, STATS = 10

Monday, June 09, 2008 3:54:14 AM (GMT Standard Time, UTC+00:00)  #    Comments [0]   SQL  | 
 Wednesday, July 20, 2005

Be sure to visit all the options under "Configuration" in the Admin Menu Bar above. There are 16 themes to choose from, and you can also create your own.

 

Wednesday, July 20, 2005 7:00:00 AM (GMT Standard Time, UTC+00:00)  #    Comments [0]   dasBlog  | 
Copyright © 2009 Software Code Help. All rights reserved.
DasBlog 'Portal' theme by Johnny Hughes.
Pick a theme: