Plugin Developer Discussion

Discussion for FogBugz Plugin developers

Plugins dir read only

Hi,

I'm back home at last so able to start testing in anger!

I've got a problem with a clean install of 7.0.1a on Vista, the Plugins directory is read only, and so are all it's children.

This means that I can't use the automatic installer script (_postbuildSln.bat) as although the example script is able to zip up the dll, it can't copy it into the upload dir, the message is "Access is denied".

Also, I can't use the example plugins build.bat, same message.

I tried looking at the properties for the Plugins dir and changing it and it's children to not be read-only, but as soon as it's finished doing its work the directories are returned to read-only?

I can however use the upload functionality in FogBugz to upload the dll or the zip file left behind by the upload script, so I can get the Hello World plugin working fine with a manual upload.

Any advice?

Thanks.
Ian Jones Send private email
Tuesday, April 21, 2009
 
 
Hi Ian,

It sounds like the FogBugz user has the correct permissions, since you're able to install a plugin using the UI.  However it sounds like your user doesn't have write permissions on the directory (as expected if you installed somewhere like C:\Program Files).

I was able to modify the permissions by doing the following:

> Start
> Computer
> Navigate to C:\Program Files\FogBugz
> Right-click Plugins directory
> Security tab
> Edit ('allow' on UAC prompt)
> Add under Users
> Enter [my user] and click ok
> Select my user at the top and check "Full control" for permissions at the bottom
> Click Ok on both dialogs

After I did this I was able to run \Plugins\examples\build.bat.
David Fullerton Send private email
Tuesday, April 21, 2009
 
 
Thanks David, "Hello, world! #4" compiles and auto-loads fine now!

However, the examples build.bat fails on building CaseLink for the WikiBlock plugin...

C:\Users\ian>cd "\Program Files\FogBugz\Plugins\examples"

C:\Program Files\FogBugz\Plugins\examples>build.bat

Building CustomFields...

Found C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bin\ResGen.exe
Read in 43 resources from "lang.resx"
Writing resource file...  Done.


wasabi -t:cd "-r:C:\Program Files\FogBugz\Plugins\examples\..\..\Website\bin\Fog
Bugz.dll" "-o:bin\CustomFields.dll"  "Plugin.was" "-r:..\..\..\Website\bin\FogC
reek.Search.dll" "/res:bin\lang.resources,CustomFields.lang.resources"

Fog Creek Wasabi Compiler version 3.0.8 (32bit Version)
Copyright (C) Fog Creek Software 2003-2009, All rights reserved.

C:\Program Files\FogBugz\Plugins\examples\CustomFields\CustomField.was(304): war
ning W0: <Server> Variable m_MyType will be a static variable, and this has weir
d semantics for ASP.NET applications. Be careful.
Found C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bin\al.exe

Creating CustomFields.zip...

adding bin\CustomFields.dll...
Saving....
That zip file (CustomFields.zip) already exists.
adding bin\CustomFields.pdb...
Saving....
That zip file (CustomFields.zip) already exists.
Adding or updating static...
adding static...
adding static\bugleft.png...
adding static\bugtop.png...
Saving....

copy "CustomFields.zip" "C:\Program Files\FogBugz\Plugins\examples\..\upload\Cus
tomFields.zip"
        1 file(s) copied.

...Build successful

Building FilterExport...

Found C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bin\ResGen.exe
Read in 1 resources from "lang.resx"
Writing resource file...  Done.


wasabi -t:cd "-r:C:\Program Files\FogBugz\Plugins\examples\..\..\Website\bin\Fog
Bugz.dll" "-o:bin\FilterExport.dll"  FilterExport.was "/res:bin\lang.resources,F
ilterExport.lang.resources"

Fog Creek Wasabi Compiler version 3.0.8 (32bit Version)
Copyright (C) Fog Creek Software 2003-2009, All rights reserved.

Found C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bin\al.exe

Creating FilterExport.zip...

adding bin\FilterExport.dll...
Saving....
That zip file (FilterExport.zip) already exists.
adding bin\FilterExport.pdb...
Saving....
That zip file (FilterExport.zip) already exists.
Adding or updating static...
adding static...
adding static\export.gif...
Saving....

copy "FilterExport.zip" "C:\Program Files\FogBugz\Plugins\examples\..\upload\Fil
terExport.zip"
        1 file(s) copied.

...Build successful

Building ProjectBacklog...

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\msbuild.exe /nologo /verbosity:qui
et /p:Configuration=Release

...Build successful

Building URLTrigger...

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\msbuild.exe /nologo /verbosity:qui
et /p:Configuration=Release

...Build successful

No build file in WikiBlock, recursing...

Building CaseLink...

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\msbuild.exe /nologo /verbosity:qui
et /p:Configuration=Release
__________________________________________________
Project "C:\Program Files\FogBugz\Plugins\examples\WikiBlock\CaseLink\CaseLink.s
ln" (default targets):

__________________________________________________
Project "C:\Program Files\FogBugz\Plugins\examples\WikiBlock\CaseLink\CaseLink.s
ln" is building "C:\Program Files\FogBugz\Plugins\examples\WikiBlock\CaseLink\Ca
seLink\CaseLink.csproj" (default targets):

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Microsoft.Common.targets(1960,9):
error MSB3011: "C:\Windows\Microsoft.NET\Framework\v2.0.50727\AL.exe" was not fo
und. Either 1) Install the .NET Framework SDK, which will install AL.exe. Or 2)
Pass the correct location of AL.exe into the "ToolPath" parameter of the AL task
.
Done building project "CaseLink.csproj" -- FAILED.

An Error has occurred.  Check the above output for more information.


C:\Program Files\FogBugz\Plugins\examples>

The output above was captured on the third attempt (hence some files already exist), the Custom Fields, Filter Export, Project Backlog and URLTrigger plugins installed OK.

I'm using a fully up to date Visual C# 2008 Express Edition on Vista Home Premium.
Ian Jones Send private email
Tuesday, April 21, 2009
 
 
The error message is a bit hard to spot, but it correctly identifies the problem:

""C:\Windows\Microsoft.NET\Framework\v2.0.50727\AL.exe" was not found. Either 1) Install the .NET Framework SDK, which will install AL.exe. Or 2) Pass the correct location of AL.exe into the "ToolPath" parameter of the AL task"

Since we're using the .NET 2.0 MSBuild, you need the .NET 2.0 SDK (which comes with VS 2005, not 2008 unfortunately).
David Fullerton Send private email
Tuesday, April 21, 2009
 
 
Thanks David, I was a bit confused because some of the plugins compiled OK using the .NET 2.0 framework, but I didn't realise I needed that SDK too.

I've downloaded and installed .NET 2.0 SDK, and now build.bat is working fine.

Thanks again David.

Ian
Ian Jones Send private email
Wednesday, April 22, 2009
 
 

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics
 
Powered by FogBugz