I was working on a feature last week that would add some event receivers to a specific list instance. (Mimi blogged kidogo kuhusu receiver kwamba orodha hapa).

Kutumia mstari amri, Mimi naweza kufunga kipengele na hakuna kosa (lakini angalia chini kwa ajili ya kosa ya siri). When I tried to deploy the feature on the site, MOSS complained of a "FileNotFoundException" kosa. This blog entry describes how I solved it.

This is the error that MOSS showed me in the web browser:

Feature ‘b2cb42e3-4f0a-4380-aaba-1ef9cd526f20’ could not be installed because the loading of event receiver assembly "xyzzyFeatureReceiver_0" failed: System.IO.FileNotFoundException: Could not load file or assembly ‘xyzzyFeatureReceiver_0’ au mmoja wa beroendet yake. The system cannot find the file specified. File name: ‘xyzzyFeatureReceiver_0’ at System.Reflection.Assembly.nLoad(AssemblyName Filename, Kamba codebase, Ushahidi assemblySecurity, Bunge locationHint, StackCrawlMark& stack udongo, Boolean throwOnFileNotFound, Boolean forIntrospection) at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Ushahidi assemblySecurity, StackCrawlMark& stack udongo, Boolean forIntrospection) at System.Reflection.Assembly.InternalLoad(String assemblyString, Ushahidi assemblySecurity, StackCrawlMark& stack udongo, Boolean forIntrospection) at System.Reflection.Assembly.Load(String assemblyString) at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject() WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) kwa 1. Kumbuka: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. Troubleshoot issues with Windows SharePoint Services.

I know how to deliberately cause that error: don’t install the assembly in the GAC. Lakini, 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% comfortable doing that because I always thought that gacutil existed for a reason … so I tried that. It made no difference.

I searched the Internets and found this post: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2243677&SiteID=1

The poster happened to be using the same root bit of code (from the Inside WSS book from this list) so that was a hopeful sign. Hata hivyo, the suggestion of decorating the assembly with an [assembly: ] 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.

Ijayo, I went to the trouble of enabling the "assembly bind failure log" (following the helpful and accurate instructions provided) 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. Lakini … it won’t search for it in the 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" for feature b2cb42e3-4f0a-4380-aaba-1ef9cd526f20: System.ArgumentNullException: Value cannot be null. Parameter jina: aina at System.Activator.CreateInstance(Type type, Boolean nonPublic) at System.Activator.CreateInstance(Type type) at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject() Troubleshoot issues with Windows SharePoint Services.

Time for one last trip to the Internets!

This time I find out, predictably enough, that MOSS issues this error because the assembly is not in GAC.

I want to get something positive out of this and try to feel a little proud that I’ve created the Fugitive of MSIL assemblies, but it’s not working. I’m just plain annoyed. I find myself muttering "chicken or the egg" under my breath.

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" but can’t find one).

I install the feature and activate it and … it works! Hivyo, after all that, I had to basically ‘reboot’ my project. This is another reason why I hate computers.

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. Kwa sababu baadhi ya, I did not use the -force option when I installed the new project. Wakati huu, I did actually, truly forget to copy this new project’s assembly into the GAC. Kama matokeo, I received that "FielNotFoundException" kosa. Wakati huu, I got it from stsadm, not when I tried to activate the feature via the web browser. Hivyo, -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.

</mwisho>

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

UPDATE 2: Katika mradi wangu wa sasa, users always upload documents. Kama matokeo, 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() receiver inaonekana kwa thamani halali ya hapo kabla ya kufanya kweli rename na tangu wakati huo, 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()" njia. Badala yake, sisi kutumia "MoveTo(…)". Here is a minimal bit of code to accomplish this:

 umma override utupu ItemAdded(SPItemEventProperties mali)
        {
            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.

Hili ni toleo la muhimu zaidi kwamba haina kitu kimoja, but assigns the name of the file to "Title":

 umma override utupu ItemAdded(SPItemEventProperties mali)
        {
            DisableEventFiring();

            // Hawawajui ilani ya bidhaa hii kwa jina la faili yenyewe.
 // NOTE: Zoezi hili lazima kuchukua nafasi kabla ya sisi kurekebisha faili yenyewe.
 // Wito update() juu ya SPFile inaonekana kubatilisha mali katika
 // baadhi ya hisia.  Updates to "Title" alishindwa mpaka mabadiliko ambayo (na update() wito)
 // walikuwa wakiongozwa mbele ya mabadiliko ya jina la faili.
            properties.ListItem["Title"] = Properties.ListItem.File.Name;

            properties.ListItem.Update();

            SPFile f = properties.ListItem.File;

            // Kupata ugani ya faili.  Tunahitaji kwamba baadaye.
 string spfileExt = mpya Picha Info(f.Name).Ugani;

            // Rename faili ID bidhaa orodha na kutumia faili ugani kuweka
 // kwamba sehemu yake intact.
            f.MoveTo(properties.ListItem.ParentList.RootFolder.Url +
                "/" + properties.ListItem["ID"] + spfileExt);

            // Kufanya hoja.
            f.Update();

            EnableEventFiring();
        }