I have a service who's app.config defines MaxMessageSize on a particular transport as a large value. The app.config generated by svcUtil changed that to 65768 (or something like that). I finally realized the problem and manually changed this. Is this just a little bug or something I shouldn't just overlook and overwrite
MaxMessageSize changed by svcUtil
Hot Topic
- visual source safe internet was not enabled on this computer because IIS is not installed
- extending ModelVisual3D
- mscorsvw will not stop running
- Help with smart tags
- Paging in toolbar off-by-one
- Upgrading from VS2005 Standard to VS2005 Professional
- Duplicating a Project within SourceSafe
- Installing Visual Studio 2005 on Windows Vista
- Remote access timeouts in VSS 2005
- Adding new property page Visual studio 2005 - strange behavior
Visual Studio
- Renaming files under source control in VS.NET
- database support
- Usercontrol Nightmare
- Generate documentation under .Net 2.0?
- Back/Forward buttons don't work in Help (Document Explorer)
- Mixed credentials: Username & Certificate
- Increase performance of ControlCollection AddControl in Word
- Unable to add the command
- Beta Toolbox is empty
- Visio and Visual Studio 2005 (Standard)
MaxMessageSize changed by svcUtil
Fdooch
koaybl
MaxMessageSize is a local-only setting and clients don't have to have the same setting as the service so it is not reflected in the service's metadata. Therefore the config generated by svcutil has a default value that the client user can change if desired.