Blog de Carlos J. Sosa M.

martes 5 de mayo de 2009

Wss 3.0 / MOSS 2007 Service Pack 2

viernes 31 de octubre de 2008

KB 958847: Cumulative update packages for the 2007 Microsoft Office core suite applications and for 2007 Microsoft Office servers: October 28, 2008

The Packages Cumulative Update for de 2008 October Contain the Latest hotfixes for the 2007 Office Core Suite Applications and Servers. We recommend that you Test hotfixes Before You deploy them in a Environment Production. Because the builds are Cumulative, Each New Release Fix CONTAINS all the Hotfixes and all the Security Fixes that were Included with the 2007 Previous Suites Office Fix Release. We recommend that you consider Applying the most Recent Release Fix that CONTAINS THE hotfix That You Need.

http://support.microsoft.com/kb/958847

jueves 30 de octubre de 2008

Errores en el EVENT LOG de Windows 2003 con MOSS 2007: Event ID 6398, 6482, 7076 y/o IIS abre en blanco

Si el servidor de MOSS experimentan alguno de estos problemas:

Al abrir IIS 6.0 Server Manager Snapin aparece en blanco
Errores en el Application Log de Windows 2003:

Event ID: 6398

El método Execute de la definición de trabajo Microsoft.Office.Server.Administration.ApplicationServerAdministrationServiceJob (ID xxx-xxxxx-xxxxxx) lanzó una excepción.

A continuación se incluye más información.

Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

Event ID: 6482

No se pudo ejecutar el trabajo de administración del servidor de aplicaciones para la instancia de servicio Microsoft.Office.Server.Search.Administration.SearchAdminSharedWebServiceInstance (xxxx-xxxx-xxx-xxx).

Motivo: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

Detalles de soporte técnico:System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. at System.DirectoryServices.Interop.UnsafeNativeMethods.IntADsOpenObject(String path, String userName, String password, Int32 flags, Guid& iid, Object& ppObject) at System.DirectoryServices.Interop.UnsafeNativeMethods.ADsOpenObject(String path, String userName, String password, Int32 flags, Guid& iid, Object& ppObject) at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail) at System.DirectoryServices.DirectoryEntry.Bind() at System.DirectoryServices.DirectoryEntry.get_IsContainer() at System.DirectoryServices.DirectoryEntries.CheckIsContainer() at System.DirectoryServices.DirectoryEntries.Find(String name, String schemaClassName) at Microsoft.SharePoint.Metabase.MetabaseObjectCollection`1.Find(String name) at Microsoft.SharePoint.Metabase.MetabaseObjectCollection`1.get_Item(String name) at Microsoft.SharePoint.Administration.SPProvisioningAssistant.ProvisionIisApplicationPool(String name, ApplicationPoolIdentityType identityType, String userName, SecureString password, TimeSpan idleTimeout, TimeSpan periodicRestartTime) at Microsoft.SharePoint.Administration.SPMetabaseManager.ProvisionIisApplicationPool(String name, Int32 identityType, String userName, SecureString password, TimeSpan idleTimeout, TimeSpan periodicRestartTime) at Microsoft.Office.Server.Administration.SharedWebServiceInstance.Synchronize() at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

Event ID : 7076

Excepción al ejecutar el trabajo del administrador del servidor de aplicaciones.

Mensaje: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

Detalles de soporte técnico:System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. at System.DirectoryServices.Interop.UnsafeNativeMethods.IntADsOpenObject(String path, String userName, String password, Int32 flags, Guid& iid, Object& ppObject) at System.DirectoryServices.Interop.UnsafeNativeMethods.ADsOpenObject(String path, String userName, String password, Int32 flags, Guid& iid, Object& ppObject) at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail) at System.DirectoryServices.DirectoryEntry.Bind() at System.DirectoryServices.DirectoryEntry.get_IsContainer() at System.DirectoryServices.DirectoryEntries.CheckIsContainer() at System.DirectoryServices.DirectoryEntries.Find(String name, String schemaClassName) at Microsoft.SharePoint.Metabase.MetabaseObjectCollection`1.Find(String name) at Microsoft.SharePoint.Metabase.MetabaseObjectCollection`1.get_Item(String name) at Microsoft.SharePoint.Administration.SPProvisioningAssistant.ProvisionIisApplicationPool(String name, ApplicationPoolIdentityType identityType, String userName, SecureString password, TimeSpan idleTimeout, TimeSpan periodicRestartTime) at Microsoft.SharePoint.Administration.SPMetabaseManager.ProvisionIisApplicationPool(String name, Int32 identityType, String userName, SecureString password, TimeSpan idleTimeout, TimeSpan periodicRestartTime) at Microsoft.Office.Server.Administration.SharedWebServiceInstance.CreateSharedWebServiceApplicationPool(SharedResourceProvider srp) at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

Revisar este documento en la Knowledge Base de Microsoft: KB 946517 .

Existe un hotfix liberado en agosto 2008 para resolver un problema del proveedor ADSI de IIS 6.0

Liberada Enterprise Library 4.1 (Octubre 2008)

Acaban de liberar la nueva versión de las Enterprise Library 4.1. A priori, se ve que han corregido algunos problemas detectados en la 4.0, proveen soporte a VS 2008 SP1 y Framework 3.5 SP1, y para los que ya estén implementando 4.0 el impacto al parecer es menor: Reasignar las referencias y nada más.

What’s New in Enterprise Library v4.1?

This release of Enterprise Library is a service release that includes the following:

– Unity interception mechanism and integration of the Policy Injection Application Block with the Unity Application Block;
– Performance improvements;
– Usability improvements to the configuration tool;
– Visual Studio 2008 Service Pack 1 support;
– Bug fixes.

Reference:
http://www.codeplex.com/entlib

If you already know and love the Enterprise Library

− check out the change log for this release;
− upgrade to V4.1—no code change is required—simply update the references to the corresponding application block assemblies and to the common assemblies;
− download the updated QuickStarts and run through the Unity-integrated examples to get the flavor of new dependency injection style of using the Enterprise Library;
− review the documentation on how to use interception with Unity;
− view webcasts on Enterprise Library and Unity, review demo code.

Reference:
http://blogs.msdn.com/agile/archive/2008/10/28/just-released-microsoft-enterprise-library-4-1-and-unity-1-2.aspx

About This Release of Enterprise Library

This release of Enterprise Library includes additions in functionality to several of the existing application blocks. The following sections discuss these and other changes in the current release. In addition, this release has been adapted to work with Microsoft Visual Studio 2008, Windows Management Instrumentation (WMI) version 2.0, and the Microsoft .NET Framework 3.5.
This topic contains the following information about this release of Enterprise Library:

Contents of This Release

This release of Enterprise Library contains the following:

Binaries. The Enterprise Library includes pre-compiled, strong-named assemblies for all the source code. For more information, see Using the Signed Binary Assemblies.

Source code. The Enterprise Library includes the source code for the application blocks, the configuration tools, the unit tests, and the QuickStarts.

Unit tests. The Enterprise Library includes the unit tests that were created while the application blocks were being developed. For more information, see Unit Tests.

QuickStarts. Enterprise Library QuickStarts are brief, easy-to-understand illustrations of key application block features. Each application block includes one or more QuickStart.

Documentation. Enterprise Library includes documentation that can be viewed with the Visual Studio Help system. The documentation includes guidance about how to use the Enterprise Library and a class library reference.

For more details, and to download these features, see the patterns & practices – Enterprise Library - Home on CodePlex.

For a complete list of the application blocks, configuration and other tools, and the core features of Enterprise Library, see Contents of Enterprise Library in the Getting Started section of this guidance.

Integration with the Unity Application Block
In this release of Enterprise Library, you can use the Unity Application Block (Unity) to intercept Enterprise Library objects and execute code before or after the body of a function or a method is executed and you can generate instances of Enterprise Library objects and inject them into other objects.
Enterprise Library contains a set of classes that allow you to obtain instances of objects such as a SqlDatabase or a CacheManager, defined in the Enterprise Library configuration, from the Unity container. In addition, new "injection-friendly" façades for some of the Enterprise Library objects replace static façades, which cannot be used with injection. These features use the dependency injection capabilities of Unity and can considerably simplify your code.

Unity provides interceptors that will, when configured in the container, allow you to intercept method calls and attach call handlers to the intercepted methods. For more information on interception see Using Interception with Unity.

For more information about the integration of Unity and Enterprise Library, see Creating Objects Using the Unity Application Block.

Changes That Affect All Application Blocks
The following changes to the Enterprise Library affect all the application blocks:

Changed: The implementation to defer the evaluation of a resource string used for configuration objects has changed. The resource strings are now evaluated at the moment the string is actually used.

Fixed: For WMI, InstallServices.bat no longer installs only the main application block assemblies. The install services script now installs the provider assemblies and performs uninstalls in the appropriate order.

Fixed: Factories that depend on locators now use explicit locks to avoid concurrency issues for the logging and the caching exception handlers. Locking was added back into the locator lookup strategy.

The following is the error message for the error that is fixed:
"The current build operation (build key Build Key[Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.ExceptionPolicyImpl, ]) failed: The current build operation (build key Build Key[Microsoft.Practices.EnterpriseLibrary.Logging.LogWriter, null]) failed: An item with the same key has already been added."

Fixed: The Install Instrumentation command on the Programs menu in Windows Vista is fixed. The updated install build script now successfully installs.

Fixed: The SystemConfigurationSource now gracefully goes to no refreshing when it cannot get the current app domain's configuration file location for the SystemConfigurationSource as is the case with the default LocalIntranet permission set. Fixed: The SqlConfiguration QuickStart now builds properly.

Fixed: Uninstalling the Windows Installer (.msi file) from non-default location now removes all the files and folders created by the installer.

Changes to the Configuration Tool
The following changes have been made to this version of the Configuration tool:

Fixed: The Edit with configuration tool menu item is fixed; it is now available when you right-click App.config or Web.config after installing Enterprise Library on Windows Server 2008 with Visual Studio 2008 and Windows Server 2003 with Visual Studio Professional Edition.

Fixed: The integrated configuration tool, which was not adding manageability provider elements to the configuration when a new manageable configuration source was added, is fixed. The design time manageability classes were changed to leverage the IPluginDirectoryProvider service to get the name of the folder containing the binaries to scan for manageability registration attributes, instead of using the AppDomain's base folder. This required moving the ConfigurationManageabilityProviderAttributeRetriever class to a design time project.

Fixed: The node for Policy Injection Application Block to save the value for "RequirePermission" is fixed. Updated the setting node mappings to use the RequirePermission flag.

Fixed: The environmental overrides tool no longer fails if the source configuration file is read-only. The save merged configuration command now succeeds even if the source configuration file is read-only.
Fixed: The stand-alone configuration tool does not fail if Federal Information Processing Standards (FIPS) compliance is enforced. The configuration console now ignores serialization if an error occurs while initializing the isolated storage file.
Changed: The Type Selector tool has changed. The Type Selector now includes the following new features:
· Ability to filter types. As you type in the Filter text box, the non-matching types are removed from the tree with assemblies.
· Ability to load assemblies from the global assembly cache. Previously, you could only load assemblies from a file.
· Ability to specify closed generic types. Previously, you could only choose the type, but now you can work up a closed generic type by choosing the generic type and its parameters in the new Type Building Tree at the top of the window.

Changes to the Caching Application Block
The following changes have been made to this version of the Caching Application Block:
Fixed: The CacheItem constructor is fixed so that both constructors initialize the expirations.
Fixed: The code now minimizes the scheduling scavenge requests and increases caching speed if the cache is over the maximum.
Fixed: The correct exception is now thrown instead of NullReferenceException when the caching section is not present in the configuration file.
Changes to the Cryptography Application Block
The following changes have been made to this version of the Cryptography Application Block:
None

Changes to the Data Access Application Block
The following change has been made to this version of the Data Access Application Block:
Changed: The OracleDataReaderWrapper class members now make the class public; this exposes all the methods available from the wrapped reader.

Changes to the Exception Handling Application Block
The following changes have been made to this version of the Exception Handling Application Block:
Changed: When building a LoggingExceptionHandler, instead of creating a logging stack every time and ignoring it if the value for the use the default logger flag on the handler is set to true, the build process now uses the value for the flag in the configuration file to create the handler with either Logging.Writer (if true) or the result of creating a new stack (if false). The handler now only knows it has a writer; it does not know where it came from.
Fixed: The DesignTime nodes for ExceptionHandlers are now handled correctly when using template-based messages. The variables are now accessed correctly when mapping an exception handler configuration object to the corresponding node and a valid configuration is saved.
Fixed: Invalid XML generated by the XmlExceptionFormatter is fixed. Exception formatters now must include the HandlingInstanceId (which is generated on each exception handling request). The way the exception formatter includes HandlingInstanceId depends on the individual formatter. The XmlExceptionFormatter adds it as an attribute of the top-level Exception element; the TextFormatter adds it as the first line of text. An ID equal to Guid.Empty can be ignored.
The logging exception handler no longer adds the exception handling ID to the message to log. The formatter handles the ID. Exception Formatter types used with the logging exception handler must now implement a constructor with the parameters TextWriter, Exception, and Guid.
There is no backward compatibility support. Creators of custom formatters must update the formatters to be used with this version so that the handling instance ID is not lost because a formatter does not support it.

Changes to the Logging Application Block
The following changes have been made to this version of the Logging Application Block:
Fixed: The WMI provider for several trace listeners now supports saving changes. WMI settings are added to support saving changes for FormattedEventLogTraceListener and FormattedDatabaseTraceListener.
Fixed: WMI support for trace listeners can now save the new Filter property to configuration objects. Logging Application Block files are updated so they can save a Filter value when pushed from WMI. WMI settings are added to support saving changes for FormattedEventLogTraceListener and FormattedDatabaseTraceListener.
Fixed: The Database trace listener no longer fails if no formatter is specified. The assembler for the FormattedDatabaseTraceListener now uses the inherited GetFormatter method, which determines whether a new formatter should be created.
Fixed: Running the logging Unity integration now works on release mode.
Added: Configuration support to opt-out of the impersonation-reverting default setting has been added. This fixes the rolling flat file trace listener problem when used in a Web application and when impersonation is enabled. To opt-out of the impersonation-reverting default mode, set the new

revertImpersonation attribute to false. The default setting is true. This supports configuration support, design time support, and manageability support (both WMI and group policy).
Fixed: Log entries with a user supplied categories collection that result in a non-serializable object is fixed. The potentially non-serializable categories collection is now copied to an array before serializing.
Fixed: The XmlLogFormatter now properly generates an XML representation of an object when that representation may contain characters that should be escaped. The XmlLogFormatter now uses an XmlWriter instead of a StringBuilder.
Fixed:FormattedTraceListenerWrapperBase now checks its filter before it forwards requests to the wrapped trace listener.
Fixed: The rolling file trace listener no longer fails when rolling for size only and the date template is empty. The log file is not truncated when the size threshold is reached. A timestamp pattern is not necessary or desired when using an increment because the increment is appended to the base file name.
Fixed: The constructor overloads for FormattedTextWriterTraceListener now use the formatter properly.
Fixed: A file name error is fixed so that the file name is now correct, fileNameWithoutExtension + .20080815.1" + extension, when the datetimepattern is set to yyyymmdd or yyyyddmm format in the rollingflatfiletracelistener.

Changes to the Policy Injection Application Block
The following changes have been made to this version of the Policy Injection Application Block:
Fixed: Design time for the policy injector collection now reads the default injector from the configuration file. The node creation classes are updated to set the default injector node property on the injectors collection node.
Changed: The matching classes implementation has changed. The implementation was moved to Unity. The classes still exist in the Policy Injection Application Block as configuration placeholders to provide backward compatibility.
Changed: The Policy Injection Application Block can now use a container. The container is configured with the Policy Injection Application Block configuration.
Changed: The Policy Injection Application Block now has only the default interceptor. Non-default interceptor options have been removed. The element has been removed. The default interception mechanism of the Policy Injection Application Block enables you to reuse existing object instances.
Changed Remoting Interception has been renamed Transparent Proxy Interception.

Changes to the Security Application Block
The following change has been made to this version of the Security Application Block:
Fixed: The documentation for the section, "Customizing the Medium Trust Policy," is fixed. The documentation now specifies in the Policy Injection Application Block that Security.Infrastructure permission is required in order to use a remoting injector.
Changes to the Validation Application Block
The following change has been made to this version of the Validation Application Block:
Fixed: The Validation Block now observes IgnoreNulls and ValidationComposition for parameter validation.
Added: The implementation of IOperationBehavior was added to the ValidationBehavior and ValidationBehaviorAttribute class. This enables you to add different rulesets to different operations in a contract.

Changes to the Unity Application Block
The following Changes have been made to this version of the Unity Application Block:
Fixed: Issues with building generic decorator chains are fixed.
Fixed: The case that a null reference exception was thrown when looking at the message property of a cross-domain BuildFailedException is fixed. BuildFailedException and ResolutionFailedException now correctly serialize cross-domain. The BuildFailedException now retrieves the serialized fields in its serialization constructor.
Added: Support was added for generic parameter injection configuration with the GenericParameter support in the InjectedMembers API. A new configuration element enables you to do the same configuration through a configuration file. Parameters and properties can now take a genericParameterName attribute. When genericParameterName is specified, only an optional dependency injection value can be set, and it cannot specify a type. Setting the genericParameterName causes a GenericParameter to be created; it uses the value set for genericParameterName and, optionally, the dependency element's name as the resolutionKey if such a dependency element exists and has a name.
Added: A PerThreadLifetimeManager was added. The container returns the same instance on the same thread and a different instance on different threads.
Fixed: Injection configuration for properties and methods is fixed. Now both default to DependencyElement.
Changed: Registered names are now available as an ObjectBuilder policy so that you can actually do a ResolveAll from within the strategy chain. The container automatically registers itself with itself.
Added: The implementation for the ResolvedArrayParameter support was added; it relies on the ResolveAll method in IUnityContainer. Both the core mechanism and the API support are implemented. Configuration support for ResolvedArray is provided with the configuration element.
Added: The new parameters, genericResolvedArray and a ParameterValue, GenericParameter, were added to the Unity configuration API for generic array support. Support for closed generics (public class MyClass) has previously existed. Support for open generics (public class MyClass) is new.
Changed: Standard typeConfig configuration no longer requires an explicit extension type in the .config file. The default extension type is used when one is not specified. The extension type is now optional.
Changed: The overloads for RegisterType now get InjectionMembers in order to configure injection without the need to call ConfigureInjectionFor.
Added:InterceptionExtension.PolicyDefinition APIs were added to provide a simplified way to wire together RuleDrivenPolicies to support interception. The general purpose API requires repeated calls to the InjectedMembers.ConfigureInjectionFor and RegisterType methods. The streamlined extension API reduces the overhead required to manage the various strings and cross links, thus making the process more obvious and convenient.
Added: Unity interception support was added, including configuration support. You can now define interceptors and when they should be used. Interceptors are defined like lifetime managers: you can just specify a type and you will get an instance of that type. You can also specify a value and, optionally, a type converter to provide more information about how the interceptor should be built.
Fixed: Type converters specified through configuration are now properly handled and do not cause issues in multi-threaded applications.
Fixed: The case that a null reference exception was thrown when looking at the message property of a cross-domain BuildFailedException is fixed. BuildFailedException and ResolutionFailedException now correctly serialize cross-domain. The BuildFailedException now retrieves the serialized fields in its serialization constructor.
Added: Support was added for generic parameter injection configuration with the GenericParameter support in the InjectedMembers API. A new configuration element enables you to do the same configuration through a configuration file. Parameters and properties can now take a genericParameterName attribute. When genericParameterName is specified, only an optional dependency injection value can be set, and it cannot specify a type. Setting the genericParameterName causes a GenericParameter to be created; it uses the value set for genericParameterName and, optionally, the dependency element's name as the resolutionKey if such a dependency element exists and has a name.
Added: A PerThreadLifetimeManager was added. The container returns the same instance on the same thread and a different instance on different threads.
Fixed: Injection configuration for properties and methods is fixed. Now both default to DependencyElement.
Changed: Registered names are now available as an ObjectBuilder policy so that you can actually do a ResolveAll from within the strategy chain. The container automatically registers itself with itself.
Added: The implementation for the ResolvedArrayParameter support was added; it relies on the ResolveAll method in IUnityContainer. Both the core mechanism and the API support are implemented. Configuration support for ResolvedArray is provided with the configuration element.
Added: The new parameters, genericResolvedArray and a ParameterValue, GenericParameter, were added to the Unity configuration API for generic array support. Support for closed generics (public class MyClass) has previously existed. Support for open generics (public class MyClass) is new.
Changed: Standard typeConfig configuration no longer requires an explicit extension type in the .config file. The default extension type is used when one is not specified. The extension type is now optional.
Changed: The overloads for RegisterType now get InjectionMembers in order to configure injection without the need to call ConfigureInjectionFor.
Added:InterceptionExtension.PolicyDefinition APIs were added to provide a simplified way to wire together RuleDrivenPolicies to support interception. The general purpose API requires repeated calls to the InjectedMembers.ConfigureInjectionFor and RegisterType methods. The streamlined extension API reduces the overhead required to manage the various strings and cross links, thus making the process more obvious and convenient.
Added: Unity interception support was added, including configuration support. You can now define interceptors and when they should be used. Interceptors are defined like lifetime managers: you can just specify a type and you will get an instance of that type. You can also specify a value and, optionally, a type converter to provide more information about how the interceptor should be built.
Fixed: Type converters specified through configuration are now properly handled and do not cause issues in multi-threaded applications.
Added: Support was added for generic parameter injection configuration with the GenericParameter support in the InjectedMembers API. A new configuration element enables you to do the same configuration through a configuration file. Parameters and properties can now take a genericParameterName attribute. When genericParameterName is specified, only an optional dependency injection value can be set, and it cannot specify a type. Setting the genericParameterName causes a GenericParameter to be created; it uses the value set for genericParameterName and, optionally, the dependency element's name as the resolutionKey if such a dependency element exists and has a name.
Added: A PerThreadLifetimeManager was added. The container returns the same instance on the same thread and a different instance on different threads.
Fixed: Injection configuration for properties and methods is fixed. Now both default to DependencyElement.
Changed: Registered names are now available as an ObjectBuilder policy so that you can actually do a ResolveAll from within the strategy chain. The container automatically registers itself with itself.
Added: The implementation for the ResolvedArrayParameter support was added; it relies on the ResolveAll method in IUnityContainer. Both the core mechanism and the API support are implemented. Configuration support for ResolvedArray is provided with the configuration element.
Added: The new parameters, genericResolvedArray and a ParameterValue, GenericParameter, were added to the Unity configuration API for generic array support. Support for closed generics (public class MyClass) has previously existed. Support for open generics (public class MyClass) is new.
Changed: Standard typeConfig configuration no longer requires an explicit extension type in the .config file. The default extension type is used when one is not specified. The extension type is now optional.
Changed: The overloads for RegisterType now get InjectionMembers in order to configure injection without the need to call ConfigureInjectionFor.
Added:InterceptionExtension.PolicyDefinition APIs were added to provide a simplified way to wire together RuleDrivenPolicies to support interception. The general purpose API requires repeated calls to the InjectedMembers.ConfigureInjectionFor and RegisterType methods. The streamlined extension API reduces the overhead required to manage the various strings and cross links, thus making the process more obvious and convenient.
Added: Unity interception support was added, including configuration support. You can now define interceptors and when they should be used. Interceptors are defined like lifetime managers: you can just specify a type and you will get an instance of that type. You can also specify a value and, optionally, a type converter to provide more information about how the interceptor should be built.
Fixed: Type converters specified through configuration are now properly handled and do not cause issues in multi-threaded applications.
Added: A PerThreadLifetimeManager was added. The container returns the same instance on the same thread and a different instance on different threads.
Fixed: Injection configuration for properties and methods is fixed. Now both default to DependencyElement.
Changed: Registered names are now available as an ObjectBuilder policy so that you can actually do a ResolveAll from within the strategy chain. The container automatically registers itself with itself.
Added: The implementation for the ResolvedArrayParameter support was added; it relies on the ResolveAll method in IUnityContainer. Both the core mechanism and the API support are implemented. Configuration support for ResolvedArray is provided with the configuration element.
Added: The new parameters, genericResolvedArray and a ParameterValue, GenericParameter, were added to the Unity configuration API for generic array support. Support for closed generics (public class MyClass) has previously existed. Support for open generics (public class MyClass) is new.
Changed: Standard typeConfig configuration no longer requires an explicit extension type in the .config file. The default extension type is used when one is not specified. The extension type is now optional.
Changed: The overloads for RegisterType now get InjectionMembers in order to configure injection without the need to call ConfigureInjectionFor.
Added:InterceptionExtension.PolicyDefinition APIs were added to provide a simplified way to wire together RuleDrivenPolicies to support interception. The general purpose API requires repeated calls to the InjectedMembers.ConfigureInjectionFor and RegisterType methods. The streamlined extension API reduces the overhead required to manage the various strings and cross links, thus making the process more obvious and convenient.
Added: Unity interception support was added, including configuration support. You can now define interceptors and when they should be used. Interceptors are defined like lifetime managers: you can just specify a type and you will get an instance of that type. You can also specify a value and, optionally, a type converter to provide more information about how the interceptor should be built.
Fixed: Type converters specified through configuration are now properly handled and do not cause issues in multi-threaded applications.
Fixed: Injection configuration for properties and methods is fixed. Now both default to DependencyElement.
Changed: Registered names are now available as an ObjectBuilder policy so that you can actually do a ResolveAll from within the strategy chain. The container automatically registers itself with itself.
Added: The implementation for the ResolvedArrayParameter support was added; it relies on the ResolveAll method in IUnityContainer. Both the core mechanism and the API support are implemented. Configuration support for ResolvedArray is provided with the configuration element.
Added: The new parameters, genericResolvedArray and a ParameterValue, GenericParameter, were added to the Unity configuration API for generic array support. Support for closed generics (public class MyClass) has previously existed. Support for open generics (public class MyClass) is new.
Changed: Standard typeConfig configuration no longer requires an explicit extension type in the .config file. The default extension type is used when one is not specified. The extension type is now optional.
Changed: The overloads for RegisterType now get InjectionMembers in order to configure injection without the need to call ConfigureInjectionFor.
Added:InterceptionExtension.PolicyDefinition APIs were added to provide a simplified way to wire together RuleDrivenPolicies to support interception. The general purpose API requires repeated calls to the InjectedMembers.ConfigureInjectionFor and RegisterType methods. The streamlined extension API reduces the overhead required to manage the various strings and cross links, thus making the process more obvious and convenient.
Added: Unity interception support was added, including configuration support. You can now define interceptors and when they should be used. Interceptors are defined like lifetime managers: you can just specify a type and you will get an instance of that type. You can also specify a value and, optionally, a type converter to provide more information about how the interceptor should be built.
Fixed: Type converters specified through configuration are now properly handled and do not cause issues in multi-threaded applications.
Changed: Registered names are now available as an ObjectBuilder policy so that you can actually do a ResolveAll from within the strategy chain. The container automatically registers itself with itself.
Added: The implementation for the ResolvedArrayParameter support was added; it relies on the ResolveAll method in IUnityContainer. Both the core mechanism and the API support are implemented. Configuration support for ResolvedArray is provided with the configuration element.
Added: The new parameters, genericResolvedArray and a ParameterValue, GenericParameter, were added to the Unity configuration API for generic array support. Support for closed generics (public class MyClass) has previously existed. Support for open generics (public class MyClass) is new.
Changed: Standard typeConfig configuration no longer requires an explicit extension type in the .config file. The default extension type is used when one is not specified. The extension type is now optional.
Changed: The overloads for RegisterType now get InjectionMembers in order to configure injection without the need to call ConfigureInjectionFor.
Added:InterceptionExtension.PolicyDefinition APIs were added to provide a simplified way to wire together RuleDrivenPolicies to support interception. The general purpose API requires repeated calls to the InjectedMembers.ConfigureInjectionFor and RegisterType methods. The streamlined extension API reduces the overhead required to manage the various strings and cross links, thus making the process more obvious and convenient.
Added: Unity interception support was added, including configuration support. You can now define interceptors and when they should be used. Interceptors are defined like lifetime managers: you can just specify a type and you will get an instance of that type. You can also specify a value and, optionally, a type converter to provide more information about how the interceptor should be built.
Fixed: Type converters specified through configuration are now properly handled and do not cause issues in multi-threaded applications.
Added: The implementation for the ResolvedArrayParameter support was added; it relies on the ResolveAll method in IUnityContainer. Both the core mechanism and the API support are implemented. Configuration support for ResolvedArray is provided with the configuration element.
Added: The new parameters, genericResolvedArray and a ParameterValue, GenericParameter, were added to the Unity configuration API for generic array support. Support for closed generics (public class MyClass) has previously existed. Support for open generics (public class MyClass) is new.
Changed: Standard typeConfig configuration no longer requires an explicit extension type in the .config file. The default extension type is used when one is not specified. The extension type is now optional.
Changed: The overloads for RegisterType now get InjectionMembers in order to configure injection without the need to call ConfigureInjectionFor.
Added:InterceptionExtension.PolicyDefinition APIs were added to provide a simplified way to wire together RuleDrivenPolicies to support interception. The general purpose API requires repeated calls to the InjectedMembers.ConfigureInjectionFor and RegisterType methods. The streamlined extension API reduces the overhead required to manage the various strings and cross links, thus making the process more obvious and convenient.
Added: Unity interception support was added, including configuration support. You can now define interceptors and when they should be used. Interceptors are defined like lifetime managers: you can just specify a type and you will get an instance of that type. You can also specify a value and, optionally, a type converter to provide more information about how the interceptor should be built.
Fixed: Type converters specified through configuration are now properly handled and do not cause issues in multi-threaded applications.
Added: The new parameters, genericResolvedArray and a ParameterValue, GenericParameter, were added to the Unity configuration API for generic array support. Support for closed generics (public class MyClass) has previously existed. Support for open generics (public class MyClass) is new.
Changed: Standard typeConfig configuration no longer requires an explicit extension type in the .config file. The default extension type is used when one is not specified. The extension type is now optional.
Changed: The overloads for RegisterType now get InjectionMembers in order to configure injection without the need to call ConfigureInjectionFor.
Added:InterceptionExtension.PolicyDefinition APIs were added to provide a simplified way to wire together RuleDrivenPolicies to support interception. The general purpose API requires repeated calls to the InjectedMembers.ConfigureInjectionFor and RegisterType methods. The streamlined extension API reduces the overhead required to manage the various strings and cross links, thus making the process more obvious and convenient.
Added: Unity interception support was added, including configuration support. You can now define interceptors and when they should be used. Interceptors are defined like lifetime managers: you can just specify a type and you will get an instance of that type. You can also specify a value and, optionally, a type converter to provide more information about how the interceptor should be built.
Fixed: Type converters specified through configuration are now properly handled and do not cause issues in multi-threaded applications.
Changed: Standard typeConfig configuration no longer requires an explicit extension type in the .config file. The default extension type is used when one is not specified. The extension type is now optional.
Changed: The overloads for RegisterType now get InjectionMembers in order to configure injection without the need to call ConfigureInjectionFor.
Added:InterceptionExtension.PolicyDefinition APIs were added to provide a simplified way to wire together RuleDrivenPolicies to support interception. The general purpose API requires repeated calls to the InjectedMembers.ConfigureInjectionFor and RegisterType methods. The streamlined extension API reduces the overhead required to manage the various strings and cross links, thus making the process more obvious and convenient.
Added: Unity interception support was added, including configuration support. You can now define interceptors and when they should be used. Interceptors are defined like lifetime managers: you can just specify a type and you will get an instance of that type. You can also specify a value and, optionally, a type converter to provide more information about how the interceptor should be built.
Fixed: Type converters specified through configuration are now properly handled and do not cause issues in multi-threaded applications.
Changed: The overloads for RegisterType now get InjectionMembers in order to configure injection without the need to call ConfigureInjectionFor.
Added:InterceptionExtension.PolicyDefinition APIs were added to provide a simplified way to wire together RuleDrivenPolicies to support interception. The general purpose API requires repeated calls to the InjectedMembers.ConfigureInjectionFor and RegisterType methods. The streamlined extension API reduces the overhead required to manage the various strings and cross links, thus making the process more obvious and convenient.
Added: Unity interception support was added, including configuration support. You can now define interceptors and when they should be used. Interceptors are defined like lifetime managers: you can just specify a type and you will get an instance of that type. You can also specify a value and, optionally, a type converter to provide more information about how the interceptor should be built.
Fixed: Type converters specified through configuration are now properly handled and do not cause issues in multi-threaded applications.
Added:InterceptionExtension.PolicyDefinition APIs were added to provide a simplified way to wire together RuleDrivenPolicies to support interception. The general purpose API requires repeated calls to the InjectedMembers.ConfigureInjectionFor and RegisterType methods. The streamlined extension API reduces the overhead required to manage the various strings and cross links, thus making the process more obvious and convenient.
Added: Unity interception support was added, including configuration support. You can now define interceptors and when they should be used. Interceptors are defined like lifetime managers: you can just specify a type and you will get an instance of that type. You can also specify a value and, optionally, a type converter to provide more information about how the interceptor should be built.
Fixed: Type converters specified through configuration are now properly handled and do not cause issues in multi-threaded applications.
Added: Unity interception support was added, including configuration support. You can now define interceptors and when they should be used. Interceptors are defined like lifetime managers: you can just specify a type and you will get an instance of that type. You can also specify a value and, optionally, a type converter to provide more information about how the interceptor should be built.
Fixed: Type converters specified through configuration are now properly handled and do not cause issues in multi-threaded applications.
Fixed: Type converters specified through configuration are now properly handled and do not cause issues in multi-threaded applications.

Reference:
http://msdn.microsoft.com/en-us/library/dd139937.aspx#Changes_That_Affect_All

Downloads & Files

Enterprise
Library 4.1 - October 2008 - StandaloneDocs.chm

Enterprise
Library 4.1 - October 2008 - PDBs.zip

Enterprise
Library 4.1 - October 2008 - Printable Docs.pdf

Reference:
http://www.codeplex.com/entlib/Release/ProjectReleases.aspx?ReleaseId=18859

martes 14 de octubre de 2008

IV Congreso Español de Usuarios de Sharepoint (C.E.U.S. IV)

El próximo 29 de octubre se celebrará en Madrid el IV Congreso Español de Usuarios de Sharepoint (C.E.U.S.), donde VASS participa como patrocinante del evento.

Este año la agenda incluye una completa gama de presentaciones repartidas en sesiones simultáneas en diferentes salas, de forma tal que los asistentes puedan elegir las mas convenientes a sus inquietudes.

Dirección:
NH Hotel Eurobuilding
Calle Padre Damián, 23
Madrid, 28036

Ver mapa en:

Registro del evento:
http://www.microsoft.com/spain/eventos/eventdetail.aspx?EventID=1032391047

AGENDA

Sesión General

09:30 - Recepción y Bienvenida
10:00 - Comienzo de las sesiones y Situación General del SharePoint
10:20 - Proyecto de Búsqueda corporativa en Repsol
10:50 - Migración de los portales del Ministerio de Industria, Turismo y Comercio de CMS a MOSS2007.
11:20 - Portal Internet Fundación Gas Natural, con accesibilidad y tecnología de Búsqueda.
11:50 - Descanso y Café
12:15 - Intranet Colaborativa y Proyecto Factoría de Innovación
12:45 - Pymec Digital, Plataforma Educativa - Redes sociales entre Profesores, Padres y Alumnos.
13:10 - Nueva tecnología Microsoft - FAST ESP
13:40 - Presentación Oficial SUGES - Grupo de usuarios de SharePoint en España
13:50 - Cierre Sesión Matinal
14:00 - Coctel
15:30 - Comienzo de las sesiones de la tarde

Sesiones de la tarde

SALA A

3:30 - 4:25 MOSS desde Cero
Veremos cómo SharePoint puede mejorar la productividad empresarial en todos los niveles de la empresa. Para ello repasaremos las principales funcionalidades del producto y su aplicación real.

4:30 - 5:25 SharePoint for internet. Web 2.0
Descubre cómo adaptar las ideas de la web 2.0 al mundo de la empresa. Convierte a tus usuarios en participantes y abre tu negocio a internet. Es hora de administrar el conocimiento.

5:30 - 6:25 ¿Trabajo más de la cuenta al diseñar flujos de trabajo?
En esta ponencia demostrar la potencia de SharePoint Designer como herramienta para el diseño de flujos de trabajo, para ellos usaremos actividades personalizadas desarrolladas con Visual Studio que, por ejemplo, nos permiten hacer el flujo más dinámico al estar asociado a un organigrama basado en listas de SharePoint.

SALA B

3:30 - 4:25 Integración Eficiente de la información formato papel en MOSS, escáneres, captura e indexación
Se mostrará todas las ventajas que se puede tener integrando la información escrita, formato papel, en MOSS. Ejemplos reales de procedimientos de captura y estimación de ahorros.

4:30 - 5:25 Mejorar la experiencia de usuario de MOSS 2007 con .NET Fx 3.5, AJAX.NET y Silverlight
La charla técnica se centrará en cómo mejorar la interfaz, la experiencia de usuario y las capacidades de SharePoint haciendo uso de éstas dos tecnologías de desarrollo.

5:30 - 6:25 Integración de MOSS 2007 en un entorno empresarial utilizando BizTalk 2006
Ponente (VASS)
La integración de SharePoint en entornos transaccionales es un reto cada vez más usual entre nuestros clientes. En esta ponencia se expondrán las distintas posibilidades de integración desde MOSS con BizTalk para el manejo de transacciones sobre múltiples sistemas existentes en la empresa.

SALA C

3:30 - 4:25 Alta Disponibilidad y recuperación de desastres en MOSS 2007
Como montar una granja de SharePoint de unos 6 servidores sobre un clúster de SQLserver 2005, como recuperar un portal completo, incluidas las personalizaciones.

4:30 - 5:25 Buenas prácticas y experiencias en proyectos de MOSS
Recomendaciones (fruto de la experiencia) para la ejecución de proyectos MOSS.

5:30 - 6:25 Actualizaciones de Infraestructura para Servidores de Office y MOSS
Como instalarlos y en qué orden. Mejoras dentro de MOSS, Mejora de la Administración, Federación. Otras mejoras del paquete a nivel de Office System (office y Project). Demostración que cubrirá la consola central de MOSS con sus mejoras (todo consolidado) además de hacer algún ejemplo de búsquedas federadas.

SALA D

3:30 - 4:25 INFOPATH, CASOS REALES DE USO EN MOSS 2007
Presentación de casuísticas reales del uso de formularios y automatización de procesos utilizando InfoPath y SharePoint Portal Server 2007.

4:30 - 5:25 SharePoint Online
Microsoft lanzará en un futuro cercano oferta de servicios hospedados de SharePoint, en esta ponencia se describirán las capacidades de éste nuevo servicio.

5:30 - 6:25 Integración con Exchange2007 y Office Communication Server
Compruebe las capacidades de integración de MOSS con las plataformas de mensajería y comunicaciones unificadas de Microsoft.

SALA E

3:30 - 4:25 Soluciones de BI integradas en Windows 2008 Hyper-V, SQL Server 2008, MOSS 2007, PPS 2007 y Excel 2007
Demostración práctica con máquinas virtuales, sobre el conjunto de tecnologías de BI de Microsoft. Modificando un Cuadro de Mandos con Excel , se muestra como se grabarán los datos en Analysis Services, y se mostraran en un cuadro de mandos en Performace Point Server, que a su vez actualizará un cuadro de Mandos en SharePoint

4:30 - 5:25 Accesibilidad: Un enfoque práctico
Garantizar la accesibilidad de sitios web basados en SharePoint se ha convertido en un requisito indispensable. En esta sesión mostraremos las diferentes certificaciones que existen al respecto, las posibilidades que SharePoint proporciona para su implementación, y algunos trucos extraídos de la experiencia en el desarrollo de sitios web accesibles basados en SharePoint.

5:30 - 6:25 Trucos, Optimización y Buenas Prácticas de SQL Server para MOSS
Gestionar y mantener las bases de datos que en una instalación de SharePoint es uno de los puntos más importantes. La gestión de grandes cantidades de documentos en la base de datos, hacen necesario aplicar determinadas tareas de mantenimiento. En esta sesión, se verán los mejores trucos para mantener la base de datos de un modo sencillo y eficiente al mismo tiempo.

SALA F

3:30 - 4:25 Microsoft Dynamics y MOSS
Ponente (VASS)
SharePoint es el centro de todas las tecnologías y productos de Microsoft. Las nuevas Ediciones de Microsoft Dynamics (ERP y CRM) profundizan aun más en ésta integración.

4:30 / 5:25 Community Kit y Podcasting para MOSS
El "Community Kit" es un conjunto de prácticas, plantillas, herramientas y código fuente que permite crear sitios basados en comunidad para prácticamente cualquier grupo de personas con un interés común. El "Podcasting Kit" facilita la fácil distribución de contenido, rico/evaluaciones/comentarios sobre contenido, la posibilidad de adjuntar contenido importante, aporta visualización web rica (similar a "Youtube" para la empresa), descargas individuales, suscripciones, búsquedas avanzadas y mucho más.

5:30 - 6:25 FAST Y MOSS
Descripción de las capacidades de búsqueda de la plataforma nueva plataforma de búsqueda FAST y las distintas posibilidades de Integración con SharePoint.

SALA G

3:30 - 4:25 Soluciones de geobúsqueda y lenguaje natural para gestionar el conocimiento empresarial con MOSS
Mediante ejemplos de aplicaciones de lenguaje natural y geo-búsqueda, se presentarán las mejores prácticas relacionadas con la puesta en marcha de proyectos de buscador en entornos internet /intranet utilizando tecnología Microsoft. Incluyendo ejemplos de cálculo de retorno de la inversión de proyectos de buscador

4:30 - 5:25 Construir aplicaciones RIA con Silverlight y Sharepoint Server
En esta charla veremos cómo lograr mejores experiencias de usuario, mediante la integración de Silverlight en nuestros portales desarrollados con Microsoft Office Sharepoint Server 2007.

5:30 - 6:25 Firma Digital y Risk Management BI en Microsoft SharePoint 2007
Sesión práctica con ejemplos de reportes de la solución de BI para la Gestión de Riesgos. Generación de reportes con Performance Point Server en formatos estándar con flujo de trabajo, firma digital durante el flujo y publicación automática en librería de documentos.

SALA H

3:30 - 4:25 Gestión de la Innovación con Enterprise Project Management y SharePoint
La gestión de la innovación se ha convertido en un valor estratégico dentro de las empresas. En esta sesión se verán las distintas capacidades de la tecnología Microsoft para la gestión de procesos de Innovación.

4:30 - 5:25 Movilidad, acceso desde dispositivos móviles
Explicación de las capacidades y configuración de MOSS para el acceso desde dispositivos móviles.

5:30 - 6:25 Citizen Service Platform - Plataforma de Servicio al ciudadano
Plataforma de servicio al ciudadano de Microsoft. Para poder transformar positivamente la experiencia del ciudadano, es necesario un cambio radical en el diseño de los procesos y un uso innovador de las nuevas tecnologías. El cambio solamente será posible al aplicar la combinación de ambas estrategias. En paralelo, la puesta en marcha de estos servicios supone un reto en el desarrollo imparable del las redes sociales, también llamadas "Web 2.0". Otras nuevas formas de presentación de la información y el conocimiento, como los sitios Web mixtos ("mashups"), "wikis", blogs, fuentes RSS y otras modalidades de software y servicios han permitido crear escenarios anteriormente inimaginables.

martes 16 de septiembre de 2008

Idiomas y Numeros de Identificacion Local para MOSS

Este numero de identificacion nos permite cambiar el idioma de la Interface de Usuario de MOSS cuando creamos plantillas (previa instalación del correspondiente Language Pack)

Lenguaje (LCID)

English-US (1033)
Spanish (3082)
Catalan (1027)
Italiano (1040)
Frances (1036)
Aleman (1031)

El resto están publicados en
http://office.microsoft.com/en-us/help/HP100305701033.aspx

Esto nos permite solventar temas como por ejemplo cambiar el idioma de los menus de una colección de sitios que hayamos creado previo a la instalación de los language packs (o si creamos un site a partir de una plantilla que está en otro idioma) ...

Si queremos por ejemplo cambiar el idioma de los menus de un sitio que estaba en un idioma X a español, simplemente ejecutamos este query en una ventana del Enterprise Manager de SQL

UPDATE [nombre base de datos de contenido].[dbo].[Webs]
SET [Language] = 3082 ,[Locale] = 3082
WHERE [Title] = 'titulo del sitio'

jueves 28 de agosto de 2008

Patterns & Practices Sharepoint Guidance

El sitio de codeplex a publicado una sección con información de cómo construir aplicaciones intranet basadas en SharePoint . Esta incluye guías de cómo arquitecturar, diseñar, y desarrollar aplicaciones así como sus best practices

Actualizado al 26-08-2008, pueden descargarlo desde:

http://www.codeplex.com/spg/Release/ProjectReleases.aspx?ReleaseId=16680

Blog de Carlos J. Sosa M.

martes 5 de mayo de 2009

Wss 3.0 / MOSS 2007 Service Pack 2

viernes 31 de octubre de 2008

KB 958847: Cumulative update packages for the 2007 Microsoft Office core suite applications and for 2007 Microsoft Office servers: October 28, 2008

jueves 30 de octubre de 2008

Errores en el EVENT LOG de Windows 2003 con MOSS 2007: Event ID 6398, 6482, 7076 y/o IIS abre en blanco

Liberada Enterprise Library 4.1 (Octubre 2008)

martes 14 de octubre de 2008

IV Congreso Español de Usuarios de Sharepoint (C.E.U.S. IV)

martes 16 de septiembre de 2008

Idiomas y Numeros de Identificacion Local para MOSS

jueves 28 de agosto de 2008

Patterns & Practices Sharepoint Guidance

ISPA

Hora Mundial

Etiquetas

Blogs Recomendados

Archivo del blog

Datos personales

Blog de Carlos J. Sosa M.

martes 5 de mayo de 2009

Wss 3.0 / MOSS 2007 Service Pack 2

viernes 31 de octubre de 2008

KB 958847: Cumulative update packages for the 2007 Microsoft Office core suite applications and for 2007 Microsoft Office servers: October 28, 2008

jueves 30 de octubre de 2008

Errores en el EVENT LOG de Windows 2003 con MOSS 2007: Event ID 6398, 6482, 7076 y/o IIS abre en blanco

Liberada Enterprise Library 4.1 (Octubre 2008)

martes 14 de octubre de 2008

IV Congreso Español de Usuarios de Sharepoint (C.E.U.S. IV)

martes 16 de septiembre de 2008

Idiomas y Numeros de Identificacion Local para MOSS

jueves 28 de agosto de 2008

Patterns & Practices Sharepoint Guidance

ISPA

Hora Mundial

Etiquetas

Suscribirse

Blogs Recomendados

Archivo del blog

Datos personales