Hi Greg,

A lot of people have been enquirying about the state of play regarding NVelocity.  The project seems o have stalled somewhat. 

See the below links regarding builds:

http://sourceforge.net/mailarchive/forum.php?threadid=7253162&forumid=12538
http://sourceforge.net/mailarchive/forum.php?threadid=7680445&forumid=12538

Also, you may consider downloading the NVelocity source code and play around with it to see if you can fix this issue!

[quote user="Greg"]I've had problems getting the MailPlugin.cs to work on installations on UNC paths.[/quote]OK, further investigation shows that it's not a NVelocity issue. It is a permission issue. Adding a simple System.IO.TextReader tr = new System.IO.StreamReader(testFile); to the MailPlugin.cs showed an exception - [quote]The referenced account is currently locked out and may not be logged on to.[/quote] (where testFile is one of the template files).

However, a standalone .aspx file running on the same server with the same code can open the file with no problems. So, my next question is, are plugins run with different credentials from the main aspx pages? I don't understand why my .aspx file can open the file, while the code in the plug-in doesn't.

Any thoughts on this are welcome,

Greg

[quote user="Greg"][quote user="Greg"]I've had problems getting the MailPlugin.cs to work on installations on UNC paths.[/quote]OK, further investigation shows that it's not a NVelocity issue. It is a permission issue. Adding a simple System.IO.TextReader tr = new System.IO.StreamReader(testFile); to the MailPlugin.cs showed an exception - [quote]The referenced account is currently locked out and may not be logged on to.[/quote][/quote]OK, I've got a bit further than this. For some reason, the GeminiPlugins.DLL runs under a different user from the standard aspx pages that call it - it's a 'feature' of ASP.NET. Unfortunately, that user doesn't have access rights to access the template files on the network path - and can't be given it (the file is on a NAS box, which can only have domain accounts applied to it and not local ones).

So, I'm going to have to modify MailPlugin.cs to fetch the template files I need using HTTP and then save them in a temporary directory on the local machine. It can then call the NVelocity.DLL pointing it at the local templates, and then delete the files. Oh well [:(]

Greg

HiGreg,

Apologies for not responding sooner.

A possible alternative could be to compile the templates as Embedded Eesources into the mail plugin DLL.  That way you can retrieve them programatically from the DLL.  I am sure that the NVelocity ResourceLocator can load templates as Embedded Resources.

Let us know how you get on.