.NET Framework

  1. Install a Managed card Managed cards are issued by businesses or organizations. They represent data (for example, credit ...
  2. Install ASP.NET version 2.0 and upgrade all application pools to ASP.NET version 2.0. The "ASP.NET 1.1" application pool ...
  3. Install optional products such as SQL Server 2005 Express Edition and the product documentation (MSDN Express Library), and ...
  4. Install scriptmaps for this version of Windows Communication Foundation at the specified path, recursively. E.g. ServiceModelReg.exe ...
  5. Install the web admin tool to the site specified by , where is the path of the site defined in IIS. If the argument is used, ...
  6. Install the web admin tool to the site specified by , where is the path of the site defined in IIS. If the argument is used, ...
  7. Install this version of ASP.NET and update scriptmaps at the IIS metabase root and for all scriptmaps below the root. Existing ...
  8. Install this version of ASP.NET and update scriptmaps at the IIS metabase root and for all scriptmaps below the root. Existing ...
  9. Install this version of ASP.NET and update scriptmaps at the IIS metabase root and for all scriptmaps below the root. Existing ...
  10. Install this version of ASP.NET. If there are any existing applications that uses ASP.NET, it will not change IIS configuration ...
  11. Install this version of ASP.NET. If there are any existing applications that uses ASP.NET, it will not update scriptmaps ...
  12. Install this version of Windows Communication Foundation and update scriptmaps at the IIS metabase root and for all scriptmaps ...
  13. Install this version of Windows Communication Foundation, register only. Do not install Windows Communication Foundation ...
  14. Install this version of Windows Communication Foundation. If there are any existing applications that use Windows Communication ...
  15. Installation failed due to the absence of a ServiceProcessInstaller. The ServiceProcessInstaller must either be the containing ...
  16. Installation of the .NET Framework 3.5 SP1 Client Profile is not supported on Windows 95. Contact your application vendor. ...
  17. Installation of the .NET Framework 3.5 SP1 Client Profile requires Windows XP SP2, Windows 2003 SP1, Windows Vista, or later. ...
  18. Installation package cannot be installed by Windows Installer. You must install a Windows service pack that contains a newer ...
  19. Installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer ...
  20. Installs the Visual Studio 2005 Designer for Windows Workflow Foundation with all debugging components. Windows Workflow ...
  21. Installs Visual Studio 2005 Designer for Windows Workflow Foundation with all debugging components. Windows Workflow Foundation ...
  22. Instance '{0}' already exists with a lifetime of Process. It cannot be recreated or reused until it has been removed or until ...
  23. Instance '{0}' cannot be run or persisted because it had a failed Dynamic Update. To run the instance, reload a fresh copy ...
  24. Instance of MessagePartDescription Name='{0}' Namespace='{1}' cannot be used in this context: required 'Type' property was ...
  25. Insufficient available memory to meet the expected demands of an operation at this time, possibly due to virtual address ...
  26. Insufficient mapping: Foreign key must be mapped to some AssociationSet or EntitySets participating in a foreign key association ...
  27. Insufficient memory to meet the expected demands of an operation, and this system is likely to never satisfy this request ...
  28. Insufficient memory to meet the expected demands of an operation, and this system is likely to never satisfy this request. ...
  29. Insufficient stack to continue executing the program safely. This can happen from having too many functions on the call stack ...
  30. Interface '%ls' is marked as dual], but does not derive from IDispatch. It will be converted as an IUnknown-derived interface. ...
  31. Interface '{0}' and '{1}' implemented on Type '{3}' are considered projected to Windows Runtime interface '{2}' and all methods ...
  32. Interface '{0}' and '{1}' implemented on Type '{3}' are considered projected to Windows Runtime interface '{2}' and all methods ...
  33. Interface '{0}' implemented on Type '{2}' is considered projected to Windows Runtime interface '{1}' and all methods on this ...
  34. Interface '{0}' implemented on Type '{2}' is considered projected to Windows Runtime interface '{1}' and all methods on this ...
  35. Interface '{0}' is not a valid MetadataView; MetadataViews do not support non-public interfaces, and interfaces that contain ...
  36. Interface '{0}' requires interface '{1}', which is not a Windows Runtime interface. Exported interfaces can require only ...
  37. InterfaceId' and 'EventsId' parameters for 'Microsoft.VisualBasic.ComClassAttribute' on '|1' cannot have the same value. ...
  38. Internal Compiler Error ( 1!8.8x! at address %3!p!): likely culprit is '%2!ls!'. An internal error has occurred in the compiler. ...
  39. Internal Compiler Error ( 1!8.8x! at address %3!p!): likely culprit is '%2!ls!'. An internal error has occurred in the compiler. ...
  40. Internal constraint exception while running constraint with name '{0}' against activity of type {1} with name '{2}'. Exception ...
  41. Internal error. An unsupported join type is in update mapping view ({0}). Only binary inner or left outer joins are supported. ...
  42. Internal error. An unsupported type ({0}) was used as an argument to cast an expression in the update mapping view. The argument ...
  43. Internal error. EntitySet ({0}) has unsupported type ({1}). Only EntitySets and AssociationSets can be processed in the update ...
  44. Internal error. Unsupported projection expression type ({0}). Only DBNewInstanceExpression projections are supported in update ...
  45. INTERNAL ERROR: Unhandled exception in Debugger::HandleIPCEvent. Event ID= x. Exception code= 08x, Eip= 08x. Process ID= ...
  46. INTERNAL ERROR: Unhandled exception in Debugger::HandleIPCEvent. Event ID= x. Exception code= 08x, Eip= 08x. Process ID= ...
  47. Internal SSL error (refer to Win32 status code for details). Check the server certificate to determine if it is capable of ...
  48. InternalsVisibleToAttribute value '{0}' in assembly '{1}' is not a valid assembly name. Use the format 'AssemblyShortName' ...
  49. Invalid anonymous type member declarator. Anonymous type members must be declared with a member assignment, simple name or ...
  50. Invalid async Begin method signature for method {0} in ServiceContract type {1}. Your begin method must take an AsyncCallback ...
  51. Invalid async Begin method signature for method {0} in type {1}. Your begin method must take an AsyncCallback and an object ...
  52. Invalid async Cancel method signature for method {0} in type {1}. Your cancel method must take no arguments and return void. ...
  53. Invalid async End method signature for method {0} in ServiceContract type {1}. Your end method must take an IAsyncResult ...
  54. Invalid async End method signature for method {0} in type {1}. Your end method must take an IAsyncResult as the last argument. ...
  55. Invalid attempt to GetBytes on column '{0}'. The GetBytes function can only be used on columns of type Text, NText, or Image. ...
  56. Invalid attempt to GetChars on column '{0}'. The GetChars function can only be used on columns of type Text, NText, Xml, ...
  57. Invalid attempt to GetStream on column '{0}'. The GetStream function can only be used on columns of type Binary, Image, Udt ...
  58. Invalid attempt to GetTextReader on column '{0}'. The GetTextReader function can only be used on columns of type Char, NChar, ...
  59. Invalid attempt to read from column ordinal '{0}'. With CommandBehavior.SequentialAccess, you may only read from column ordinal ...
  60. Invalid binding element type for binding element extension configuration object. This binding element extension manages configuration ...
  61. Invalid binding type for binding extension configuration object. This binding extension manages configuration of binding ...
  62. Invalid category name. Its length must be in the range between '{0}' and '{1}'. Double quotes, control characters and leading ...
  63. Invalid contract definition: one-way operation has TransactionFlowOption set to Mandatory in operation '{0}' of contract ...
  64. Invalid counter name. Its length must be in the range between '{0}' and '{1}'. Double quotes, control characters and leading ...
  65. Invalid data encountered. A required relationship is missing. Examine StateEntries to determine the source of the constraint ...
  66. Invalid DeleteOnNull specification for member '{0}'. DeleteOnNull can only be true for singleton association members mapped ...
  67. Invalid element in configuration. The extension name '{0}' is not registered in the collection at system.serviceModel/extensions/{1}. ...
  68. Invalid endpoint type for endpoint extension configuration object. This endpoint extension manages configuration of endpoint ...
  69. Invalid enum value '{0}' cannot be deserialized into type '{1}'. Ensure that the necessary enum values are present and are ...
  70. Invalid file name for file monitoring: '{0}'. Common reasons for failure include: - The filename is not a valid Win32 file ...
  71. Invalid file name for file monitoring: '{0}'. Common reasons for failure include: - The filename is not a valid Win32 file ...
  72. Invalid function pointer 1$x was passed into the runtime to be converted to a delegate. Passing in invalid function pointers ...
  73. Invalid IContextChannel passed to OperationContext. Must be either a server dispatching channel or a client proxy channel. ...
  74. Invalid image URL format. #SEQ formatter must be followed by (300,3), where 300 is a max sequence number (between 0 and 9999999) ...
  75. Invalid internal state machine execution state. The calculated execution path to the current state does not match the actual ...