Wcf Generic Command For Vista Setup

17-04-2021 admin

-->

Developer Community| License Terms| Blogs| Known Issues

Visual Studio 2017 15.3 Preview 1 included templates for VB class libraries targeting.NET Standard class libraries and for.NET Core console apps. With the release of.NET Core 2.0 today those templates go-live. The.NET Standard You can use the built-in templates to create cross-platform command-line apps, as well as creating and testing.
The DHS Acronyms, Abbreviations, and Terms (DAAT) list contains homeland security related acronyms, abbreviations, and terms that can be found in DHS documents, reports, and the FEMA Acronyms, Abbreviations, and Terms (FAAT) list.
The Devenv.exe command in Visual Studio 2010 hangs randomly while a Setup project is built from a command line. The IDE crashes when you close a Setup project or a Deployment Projects Setup project. The RestartWWWService=false command incorrectly restarts the WWW service on a computer that is running Windows Server 2003 when projects are built.

Wcf generic command for vista setup download

Creating a WCF Service Library in Visual Studio 2008 on Vista x64 is troublesome when referencing an x86 DLL. A service that calls a 32-bit DLL is required to have a platform target of x86 to run on a. An extension only available in Windows Vista and newer (7, 8, 8.1 and 10), called Direct3D 9Ex (previously versioned 9.0L (L - codename Windows Longhorn)), allows the use of the advantages offered by Windows Vista's Windows Display Driver Model (WDDM) and is used for Windows Aero.

Note

This is not the latest version of Visual Studio. To download the latest release, please visit the current release notes for Visual Studio 2019.

Download Visual Studio 2010 Service Pack 1

To download Visual Studio 2010 Service Pack 1, click on the download button. The files are downloaded from our free Dev Essentials subscription-based site. Please see the Dev Essentials page for information on our free comprehensive developer program and services.

Visual Studio 2017 2010 Service Pack 1 Release Notes

released on August 18, 2011

What's New in this Release

About Visual Studio 2010 Service Pack 1

Summary: Improvements in this Release

Summary: Issues Fixed in this Release

About Visual Studio 2010 Service Pack 1

Supported Operating Systems

Windows Server 2008 R2 (x64-based)
Windows 7 (x86-based and x64-based)
Windows Server 2008 (all x86-based and x64-based editions) together with Service Pack 2
Windows Vista (all x86-based and x64-based editions except Starter Edition) together with Service Pack 2
Windows Server 2003 R2 (all x86-based and x64-based editions)
Windows Server 2003 (all x86-based and all x64-based editions) together with Service Pack 2

Note

You must have MSXML 6.0 installed to apply this service pack on a computer that is running Windows Server 2003. For more information about how to obtain MSXML 6.0, visit the Microsoft Core XML Services (MSXML) 6.0 website.

Windows XP Service Pack 2 (SP2) or a later version of Windows XP
Windows XP (all x86-based editions except the Starter edition) together with Service Pack 3

Supported Architectures

32-bit (x86)
64-bit (x64) (WOW)

Hardware Requirements

1.6 gigahertz (GHz) or faster processor
1,024 MB RAM (1.5 GB if running in a virtual machine)
5.5 GB of available hard-disk space
5,400 RPM hard disk drive
DirectX 9-capable video card that is running at 1,024 × 768 or higher-resolution display
DVD drive

Software Requirements

You must have one of the supported Visual Studio 2010 programs that are listed in the 'Applies to' section installed to apply this service pack.

Details: Improvements in this Release

Visual Studio 2010 SP1 includes an update to the Microsoft .NET Framework 4. For more information about the update, read the Microsoft Knowledge Base article 2468871 Update for Microsoft .NET Framework 4.

Debugging Improvements

Visual Studio 2010 SP1 adds the following improvements:

Improvements when mini dump files and debugging mini dump files are opened.
Improvements to reduce hangs when attaching a process.
Reliability improvements in message passing interface (MPI) debugging.
Thread slipping improvements during function evaluation.

MFC-based GPU-accelerated Graphics and Animations

Visual Studio 2010 SP1 enables the following two technologies for MFC:

Direct2D, a hardware-accelerated, immediate-mode, 2-D graphics API that provides high performance and high-quality rendering for 2-D geometry, bitmaps, and text. For more information, read the Direct2D article.
Windows Animation Manager, which enables rich animation of user interface elements. For more information, visit Windows Animation Manager.You can take advantage of these two technologies without breaking the MFC programming model. Additionally, you can find demos in the following directory:drive:</strong>Program FilesMicrosoft Visual Studio 10.0Samples1033VC2010SP1Samples.zipFor more information about the technology improvements in Visual Studio 2010 SP1, see MFC Additions for Visual Studio 2010 SP1.

New AMD and Intel instruction Set Support

Visual Studio 2010 SP1 adds intrinsic functions or intrinsics to enable the extensions on the AMD and Intel new microprocessors that will be released next year. The intrinsic functions allow for highly efficient computing without the overhead of a function call. For more information about the intrinsics function, see the Compiler Intrinsics article.For more information about the extensions, visit the Intel AVX third-party website.

SQL Updates

Data-Tier Application Project:

Style IntelliSense

Lets you easily modify styles that you already have in XAML. Now you get IntelliSense for properties and their values in a style that is based on the TargetType.

Data Source Selector

Lets you easily select and modify the data source information directly from the design surface.

Advanced Grid Commands

Lets you easily add, remove, and reorder grid rows and columns.

New Thickness Editor

Lets you bulk edit specific items such as margins or padding on multiple controls.

Sample Data Support

Lets you add sample data to see your item templates and bindings light up at design time. Not only does this make hooking up data bindings easier through the Data Binding Picker, it also means that you can design size-to-content and auto layouts much more smoothly. Also, the design time data will flow cleanly between Visual Studio and Expression Blend.

Increased Stability

Many stability improvements were made to Visual Studio 2010 SP1.

Details: Issues Fixed in this Release

.NET

ASP.NET Editor

The BACKSPACE key and the ARROW keys do not work.
Devenv.exe crashes, and an Access Violation error occurs, during *.js auto-formatting.
Problems in the 'Format Document' command in the JScript Code Editor.
The JScript object member is not listed in IntelliSense when the object member contains a $ character.
The 'Inner' function does not parse correctly. The function returns the 'Undefined' command incorrectly when a JScript file is referenced.
JScript function formatting problems occur.
JScript IntelliSense does not work as expected when it augments an object that is defined by the 'Reference' tab.
XML comments do not appear in JScript IntelliSense.

Architecture Tools

The sequencing of diagrams, the rearrange of the layout, and Lifelines are not resized as expected.
You receive the 'Item with same key already added' message in a Sequence diagram.
Interaction use is missed after the Lifeline group is expanded.
You cannot open a diagram if you change an interface's fully qualified name, and the Hide qualified name option is set to True. In this case, a realization to the interface is displayed as a lollipop.
Validation is broken for generic parameter references inside a method body.
Modeling project allows users to create duplicate named references. This problem can lead to project corruption.
A null reference error occurs for explicit interface implementations and transient diagrams when you generate a sequence diagram.

Additionally, Visual Studio 2010 SP1 contains the following improvements:

Interaction Messages are now sorted.
Backlinks to layer diagram elements from Team Foundation Server work items are now supported.

Coding

C Runtime (CRT)

MSPDB100.dll is dynamically loaded, but the DLL does not specify a fully qualified path in the CRT.
When the the WEOF constant is passed to the 'swprintf_s' function, the buffer does not receive a NULL termination.

Additionally, Visual Studio 2010 SP1 contains the following improvements:

Performance and stability improvements.
More efficient memory management.
Other IDE improvements to prevent user interface (UI) freezes and crashes.
Performance improvement for the F12 (Goto Definition) function key on large projects.

C# Compiler

An Access Violation occurs when you debug a C# structure that has about 500 fields.
Designers may not correctly qualify types in code that is emitted.

C# Editor

Visual Studio 2010 crashes when it writes code at design time.
The MVC3 Razor release candidate may cause an invalid code block indention when the release candidate autoformats a document.
In WPF projects, the C# IntelliSense service may crash on shutdown.
If the Multi-targeting Pack is not installed, the C# language service crashes when you try to load a project.
The 'Highlight References' command causes a crash in some cases when a file is being closed.
Generate type can cause a crash report when you open the generated file.
Smart tags can cause a crash report in some web scenarios.
A crash report occurs when you change the Public field to Property.
When you pause the pointer over a named argument, QuickInfo crashes if the method name matches the local class name.
C# IntelliSense crashes when the Solution Navigator extension is installed, and an 'aspxweb' page is opened as an extra file.
The BACKSPACE key does not work correctly for Korean characters in the Text Editor.

C++ Compiler

C++ compiler generates incorrect movups instructions instead of movss instructions.
There is a specific problem with the /Og option in the 64-bit version of Visual Studio 2010 Beta 2 compiler.
SSE2 instructions are generated when the /arch:SSE option is specified.
There are specific problems in the x64 version of the C++ compiler (optimizer).
Destructor calls are missing when optimization is enabled.
The compiler crashes with the 'decltype(*this)' type specifier.

Additionally, Visual Studio 2010 SP1 contains the following improvements:

Optimizations and fixes in several code generation areas.
Managed Incremental Build parity with Visual Studio 2008. Previously, the Enable Managed Incremental Build property did not exist when you opened the Project Properties pages for a Visual C++ 2010 project.

C++ Debugging

Mixed call stacks are broken when you debug C++ code.
When you try to inspect local variables while you are debugging in Visual Studio 2010, you receive a 'CXX0017 'Symbol not found' error message.
The Watch window displays incorrect values.

C++ Editor

Visual Studio 2010 crashes in a C/C++ project when hiding or showing all files of solution.
Class member auto-completion forces wrong member (case-sensitive).
Go to Declaration is slow in some cases.
The C++ Editor may crash when you insert comments.
A crash occurs while declaring C++ enumuneration.
Issues occurred in native IntelliSense, such as with indexes and reporting.
The NavigateTo method in C++ occasionally becomes unresponsive.

Standard C++ Library

The 'vector::erase' constraint returns an incompatible iterator in the debug build.
The * of the 'tr1:regex' constraint differs in Visual Studio 2008 and in Visual Studio 2010 when some regular expressions are used.
When you use the “std::vector' statement, a memory leak occurs when you run your program.

Concurrency Runtime

Fixed concurrent queue access violations.
Visual C++ concurrent runtime libraries leak memory in Visual Studio 2010.

Additionally, Visual Studio 2010 SP1 contains the following improvements:

Incorrect positive memory leaks are no longer reported when you use Concurrency Runtime (ConcRT).
The '__stdcall' calling convention is now supported by all PPL, ConcRT, and concurrent containers.
An access violation does not occur on 'concurrent_queue' with 'std::string.'
Associated containers can be used with the 'parallel_for_each' function.

Code Analysis

538887: Visual Studio crashes occur when you view Code Analysis Settings for Solution that has an IIS site.
The Static Code Analyzer reports valid code.
Frequent crashes occur when you change Code Analysis settings in Visual Studio Team Server 2010.

Additionally, Visual Studio 2010 SP1 contains the following improvement:

Managed Code Analysis (FxCop) now installs on x64 TeamBuild servers.

Code Discovery and Validation

Crashes that occur with graph navigation are fixed.
A scroll-bar UX issue inside the Architecture Explorer’s advanced selection menu is fixed.
Temporary files remain after layer validation is run.
The 'Contained By' action on a C++ folder may cause Architecture Explorer to crash.

Entity Framework (Code Generation)

Problems occur when you use Entity Framework Self Tracking Entities together with AppFabric CACHE (‘Velocity’) and the .NET Framework 4.0 release version.
When you use an Edmx file together with ADO.NET, the Self-Tracking Entity Generator causes generated files that cannot be compiled because of a missing HandleCascadeDelete event handler.
A Self-Tracking Entity Template does not generate code for function imports that do not have a return value.
An Entity does not get marked as modified when an FK association that uses the EntityReference.EntityKey property is nulled.
A Self-Tracking Entities Template generates incompatible code for dot-separated namespaces.
A Self-Tracking Entities Template does not generate default values for scalar properties on complex types.
Miscellaneous code-generation changes to comply with Visual Basic pretty-lister guidelines.

F#

Visual Studio 2010 SP1 fixes issues with stability of the compiler and code correctness for generated code. For example, this service pack fixes calling convention correctness for platform invoke and emitting XML document comments for extension methods. Additionally, this service pack improves the performance of generating an event hook up.

JScript Editor

Extra space is added under the code when the Keep tabs option is selected.
Indentation is incorrect for empty object literals.
The JScript function formatting option Parens does not function as 'worded parentheses.'
The keyboard shortcut ALT+A is used incorrectly for the Insert space after function keyword for anonymous functions command.
Atlas IntelliSense is not present when script manager has a ServiceReference http path.
The memory of the Visual Studio process increases to 300 MB when you open another project, you leave the current project open, and the current project has lots of JScript files that are opened.
No IntelliSense exists inside a ForIn condition.
Very large memory growth occurs when you comment or uncomment large JScript files.
Typing is very slow in a JScript file that has long content on one line.
Global members that come from external files cannot find IntelliSense.
Loss of colorization and IntelliSense occurs after you update IntelliSense to reference a remote or non-existing service.

Microsoft Foundation Classes (MFC) and Active Template Library (ATL)

In the CDatabase/Crecordset MFC, the 'DoFieldExchange' variable does not work correctly in Visual Studio 2010.

Additionally, Visual Studio 2010 SP1 improves security and performance and provides other improvements in ATL/MFC.

Visual Basic Compiler

A crash may occur when you type near the ReadOnly property, and multiple field declarations are present.
When any local's type comes from a signed assembly, Visual Basic does not show values in the Locals window.
In large projects that contain many XML doc comments, you may experience delays in the editor when you type.
When you switch the focus between expression fields, you may experience delays in large Workflow Foundation projects.

Visual Basic Editor

Mandatory ByVal is displayed in Visual Basic .NET.
IntelliSense Enum values are not shown.
A large Visual Basic project may crash when it is closed.
The Visual Studio IDE becomes unresponsive when it parses XMLDOC comments in a complex project.
The Visual Basic Language Service crashes when you open a web project.

Windows Forms Designer

You use the Visual Studio 2010 IDE to open a project that is in an earlier version. For example, you open a Visual Studio 2008 project. After a debug session, you cannot rebuild or debug the project again, and you receive an error message that resembles the following:

Unable to copy file objDebugassembly_name to binDebugassembly_name. The process cannot access the file binDebugassembly_name because it is being used by another process.

If you rename or undo a paste of Windows Forms controls in the designer, the designer file leaks during the Visual Studio 2010 instance.
You upgrade a Visual Studio 2005 project to Visual Studio 2010, and you retarget the project to the .NET Framework 4. When you close the Visual Studio instance, a supported language version of Visual Studio may crash.

Database Projects

Database Project deployment fails when you try to revoke permissions by using the GRANT OPTION permission.
Customized .dbschema files that contain nonprintable characters cause Visual Studio to crash when you try to upgrade a model.
The 'Schema Compare' feature ignores composing children when the Only compare elements that exist in the source item is enabled.
An Incremental Database Project deployment becomes unresponsive when the project contains long check constraints that have to be normalized.
Index Hints do not resolve across database references in a database project build.

Debugger

Debugger randomly treats 'step-into' and 'step-over' procedures as a 'run to completion' procedure.
Visual Studio 2010 hangs after several debugging sessions, and a blank Windows Internet Explorer window appears.
Pinned debug values.
Visual Studio crashes when it imports the same Data Tip that was previously exported.
When you perform client-side debugging, you receive the following error message:

Tip

Error: The breakpoint will not currently be hit. This location could not be mapped to client side script.

Only 100 'std::map' elements are allowed in the debugger.
Using Source Server tagged PDBs causes Visual Studio 2010 to hang and then crash.
Some issues on event tracing in Windows Presentation Foundation (WPF) are fixed.

IntelliTrace

Log files are removed for the Disk Cleanup operation.
Crashes that were introduced in customer's application are fixed.
A crash that occurs when you switch to the Disassembly window you enter Historic Mode is fixed.
Crash-on-exit because of putting a trace file in Run mode is fixed.####IntelliTrace for 64-bit and SharePointIntelliTrace is the revolutionary new debugging technology in Visual Studio 2010 that enables you to move forward and backward through a debug session. However, because of time constraints and because it is a completely new feature, this technology does not work in all scenarios.Visual Studio 2010 SP1 enables the IntelliTrace debugging technology on 64-bit solutions and for Microsoft SharePoint farm solutions.

Profiler

The Performance Explorer does not load when multiple Visual Studio instances are started.
JScript profiling does not work on Russian and other European and Latin American language operating systems.
JScript profiling does not work with Windows Internet Explorer 9.
Visual Studio crashes when you profile a Web Application project by using a customer web server setting.

Additionally, Visual Studio 2010 SP1 contains the following improvements:

More accurate sampling in Hyper-V.
Improved JavaScript profiling to enable profiling of multiple processes.
Improved stability it performs 64-bit profiling.

Setup Projects

The Registry Capture Utility crashes on a computer that is running Windows 7.
Visual Studio may crash when you configure prerequisites.
A Setup project compilation fails when you run it from the command line.
Migrating Setup projects from Visual Studio 2008 to Visual Studio 2010 changes component GUIDs, and this causes the upgrades to fail.
The Devenv.exe command in Visual Studio 2010 hangs randomly while a Setup project is built from a command line.
The IDE crashes when you close a Setup project or a Deployment Projects Setup project.
The RestartWWWService=false command incorrectly restarts the WWW service on a computer that is running Windows Server 2003 when projects are built by using Visual Studio 2010.

T4

Visual Studio 2010 SP1 contains the following improvements:

Customize or extend T4 templates by using template inheritance.
Use helper libraries with T4 much more easily because T4 no longer locks referenced assemblies in memory.
Deploy T4 to your build server for build-time generation.

ASP.NET Data

In the Release Candidate for Visual Studio 2010, the 'DataContext' field is not visible when the 'Show only DataContext objects' check box is selected.

Web Development

Web Projects

The ASP.NET App_Themes folder does not allow for adding a new CSS style sheet.
The .designer.cs style sheet does not work as expected with nested web application projects.
SCC glyphs are not displayed in Solution Explorer.

HTML Designer

Style sheets that are external to a web application are not applied in Visual Studio .NET 2010 IDE design view.
HTML Designer cannot be used as expected to design web pages.

Windows Phone Developer Tools

The deployment of XAP files over 64 MB may fail for testing and debugging on physical telephone devices.

General WPF and Silverlight Designer

When you use the 'Choose Toolbox Items' dialog box, you must manually kill the process, the application becomes unresponsive, and data loss and GUI corruption occur.
The IDE locks completely when you try to add Silverlight items to the toolbox.
Upgrading Silverlight while Visual Studio is running causes Visual Studio to crash.
Deleting controls that have a background thread running causes Visual Studio to crash.
The error list is not displayed when XAML files that contain errors are opened.

Additionally, Visual Studio 2010 SP1 contains the following improvements:

Performance improvements when you select a different color profile are added.
The Save dialog box appears when you close a solution after an event in Visual Basic is generated.
Support for portable assemblies is added.

XAML

XAML Designer Design Surface