I was working on a feature last week that would add some event receivers to a specific list instance. (Eu escribín un pouco sobre esta lista receptor aquí).

Usar a liña de comandos, Podería instalar o recurso sen erro (pero mira abaixo o erro oculto). When I tried to deploy the feature on the site, MOSS complained of a "FileNotFoundException" error. This blog entry describes how I solved it.

Este é o erro que Moss me mostrou o navegador web:

Feature ‘b2cb42e3-4f0a-4380-aaba-1ef9cd526f20’ could not be installed because the loading of event receiver assembly "xyzzyFeatureReceiver_0" fracasado: System.IO.FileNotFoundException: Could not load file or assembly ‘xyzzyFeatureReceiver_0’ ou unha das súas dependencias. O sistema non pode atopar o ficheiro especificado. O nome do ficheiro: ‘xyzzyFeatureReceiver_0’ at System.Reflection.Assembly.nLoad(AssemblyName filename, Codebase cadea, AssemblySecurity evidencia, Asemblea locationHint, StackCrawlMark& apilar solo, Booleana throwOnFileNotFound, ForIntrospection Boolean) at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, AssemblySecurity evidencia, StackCrawlMark& apilar solo, ForIntrospection Boolean) at System.Reflection.Assembly.InternalLoad(Cordas assemblyString, AssemblySecurity evidencia, StackCrawlMark& apilar solo, ForIntrospection Boolean) at System.Reflection.Assembly.Load(Cordas assemblyString) at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject() WRN: Rexistro de conexións de assembly está desactivado. Para activar o rexistro de erros de assembly, definir o valor de rexistro [HKLM Software Microsoft Fusion!EnableLog] (DWORD) para 1. Nota: Hai algunha perda de rendemento asociada ao rexistro de fallo de conexión de assembly. Para desactivar este recurso, elimine o valor do Rexistro [HKLM Software Microsoft Fusion!EnableLog]. Solucionar problemas con Windows SharePoint Services.

Sei como facer que deliberadamente este erro: don’t install the assembly in the GAC. Pero, it was in the GAC. I normally install assemblies into the GAC by dragging them into the c:\windows\assembly folder using windows explorer. I’ve never felt 100% cómodo facendo iso, porque eu sempre pensei que Gacutil existiu por unha razón … so I tried that. It made no difference.

Eu procurei as Internets e atopei este post: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2243677&SiteID=1

O cartel pasou a ser co mesmo bit raíz do código (do libro WSS Dentro desta lista) so that was a hopeful sign. Con todo, a suxestión de decorar a montaxe cunha [montaxe: ] directive didn’t make sense to me. I tried it anyway and I was right. It made no difference.

Then I noticed that my class definition was not public. I made it public and that made no difference.

Seguinte, I went to the trouble of enabling the "assembly bind failure log" (seguindo as instrucións útiles e precisas proporcionadas) and this is where things started to get interesting. That log shows me that the runtime is searching everywhere on that server for my assembly. It even appears to be searching for it in my medicine cabinet. Pero … non vai buscalo no GAC.

I put on my winter jacket and go searching the Internets again and find that someone has had this problem too. The lengthy discussion in that posting peters off into nothing and I can’t find a solution.

I move my assembly into one of the places the log claims it’s searching and I make a little more progress. I’m rewarded with a new error in the browser when I try to activate the feature:

Failed to create feature receiver object from assembly "xyzzyFeatureReceiver_0", type "Conchango.xyzzyFeatureReceiver" ao recurso de b2cb42e3-4f0a-4380-aaba-1ef9cd526f20: System.ArgumentNullException: O valor non pode ser nulo. O nome do parámetro: tipo at System.Activator.CreateInstance(Tipo Tipo, Booleana nonPublic) at System.Activator.CreateInstance(Tipo Tipo) at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject() Solucionar problemas con Windows SharePoint Services.

Tempo para unha última viaxe para as Internets!

Esta vez descubro, previsiblemente, that MOSS issues this error because the assembly is not in GAC.

Quero aproveitar algo positivo deste e tentar sentir algo orgulloso de que eu creei o Fugitivo de conxuntos MSIL, but it’s not working. I’m just plain annoyed. I find myself muttering "chicken or the egg" baixo a miña respiración.

I finally decide to punt. I create an entirely new project and copy/paste the code from the incredible-cloaked-from-the-GAC-assembly non-working project over to this new project. (I look for a build flag called something like "hide from assembly binding if installed in the GAC" pero non pode atopar un).

Eu instalar recurso e activa-lo e … funciona! Así, despois de todo isto, I had to basically ‘reboot’ my project. Esta é outra razón pola que eu odio ordenadores.

I did learn something useful from this. I had been installing features using the stsadm command line all day long and been using the "-force" option out of habit. Por algunha razón, I did not use the -force option when I installed the new project. Este tempo, Eu fixen realmente, truly forget to copy this new project’s assembly into the GAC. Como resultado, I received that "FielNotFoundException" error. Este tempo, I got it from stsadm, not when I tried to activate the feature via the web browser. Así, -force actually plays two roles. It allows you to re-install an existing feature. It also allows you to install a buggy feature that cannot work at runtime by suppressing the error. It probably says as much in the help somewhere but I never noticed it.

</final>

Actualización: This works but there are significant limitations which are described in the comments. This may still be useful in some cirumstances.

Actualización 2: O meu proxecto actual, users always upload documents. Como resultado, I don’t run into a problem where MS Word is running and thinks that the file was renamed on it. I did run into a problem, "the file was modified by someone else" and solved this via a simple semaphore type flag. Users need to change a meta data field from its default value to something else. The itemupdated() receptor busca por un valor válido alí antes de realmente facer a renomeação e desde entón, I have not had any problems. Your mileage may vary.

I have a client requirement to change the name of files uploaded to a specific document library to conform with a particular naming convention. The API does not provide a "rename()" método. Pola, usan "MoveTo(…)". Here is a minimal bit of code to accomplish this:

 público substituír invalidar ItemAdded(SPItemEventProperties Propiedades)
        {
            SPFile f = properties.ListItem.File;

            f.MoveTo(properties.ListItem.ParentList.RootFolder.Url + "/xyzzy.doc");
            f.Update();

        }

The only tricky bit is the "properties.ListItem.ParentList.RootFolder.Url". The MoveTo() method requires a URL. That mashed up string points me to the root folder of my current document library. This allows me to avoid any hard coding in my event receiver.

Esta é unha versión máis útil que fai o mesmo, but assigns the name of the file to "Title":

 público substituír invalidar ItemAdded(SPItemEventProperties Propiedades)
        {
            DisableEventFiring();

            // Asignar o título deste artigo para o nome do ficheiro en si.
 // NOTA: Esta asignación debe ocorrer antes de modificar o propio arquivo.
 // Chamando actualización() no SPFile parece invalidar as propiedades en
 // nalgún sentido.  Updates to "Title" puido ata que o cambio (e actualización() chamar)
 // foron movidos fronte á mudanza do nome do ficheiro.
            properties.ListItem["Title"] = Properties.ListItem.File.Name;

            properties.ListItem.Update();

            SPFile f = properties.ListItem.File;

            // Obter a extensión do ficheiro.  Necesitamos que máis tarde.
 corda spfileExt = novo FileInfo(f.Name).Extensión;

            // Renomeie o ficheiro para a identificación do elemento da lista e utilizar a extensión do ficheiro para manter
 // que parte dela intacta.
            f.MoveTo(properties.ListItem.ParentList.RootFolder.Url +
                "/" + properties.ListItem["ID"] + spfileExt);

            // Comprometer o movemento.
            f.Update();

            EnableEventFiring();
        }