Hi Nick, lol, I was about editing my post in the same second your reply popped up :)
Yes of course. Otherwise it won't even compile.
-Ingvar

So does that fix it or not?

Hi Nick, I am talking about compiled extensions, DLLs.
If a there were a typo in the namespace, I wouldn't even be able to compile my extension.
If anyone here has successfully compiled a (simple as possible) Vegas Extension that will show up in the Vegas 14 menu, I am very interested to know how you did it. Possibly with source code.

I use this folder, please tell me if it is the wrong folder:
C:\Users\my-user-name\AppData\Local\Vegas\Application Extensions

-Ingvar
 

Try this folder: C:\ProgramData\VEGAS Pro\Application Extensions

This is where version independent Extensions can be placed in SVP v13 and earlier.
C:\Users\USERID\Documents\Vegas Application Extensions

Try this folder: C:\ProgramData\VEGAS Pro\Application Extensions

This contradicts the information given in Vegas 14 help, which says:

Vegas Pro extensions are saved in C:\Users\user name\AppData\Local\Vegas\ Application Extensions

There is a space before "Application", this has to be an error in the help file.

-Ingvar

FALSE😉
as altarvic wrote:
C:\ProgramData\VEGAS Pro\Application Extensions
there are all my working extensions

I reference Vegas.dll

I reference Vegas.dll

I reference Vegas.dll

There is no such thing as Vegas.dll

-Ingvar

Sony Vegas Pro v8 to v13 Extensions use Vegas.dll.  My Timeline Tools extension is placed in
C:\Users\USERID\Documents\Vegas Application Extensions and Scripts can be placed in
C:\Users\USERID\Documents\Vegas Script Menu.

Hi Gary, the title of this topic is:
"My home made Extension won't show up in Vegas 14"

I have written dozens of vegas extensions for several years. All fine on all Vegas versions, except Vegas 14. So if anyone here successfully has compiled and run extensions for Vegas 14, I am very interested in discussing this further!

-Ingvar

maybe you'll get info from http://www.semw-software.com/en/extensions/
He changed his extensions for VP14.
(and they are now in C:\ProgramData\VEGAS Pro\Application Extensions)

https://www.vegascreativesoftware.info/de/forum/semw-extensions-for-vegas-14--103967/

Try this folder: C:\ProgramData\VEGAS Pro\Application Extensions

This contradicts the information given in Vegas 14 help, which says:

Vegas Pro extensions are saved in C:\Users\user name\AppData\Local\Vegas\ Application Extensions

There is a space before "Application", this has to be an error in the help file.

-Ingvar

Did you try it or not? 

I tried it. But I think this is not the fault. I must be doing somerthing else wrong. And only for Vegas 14. When I try to debug, attaching Vegas 14 to Visual Studio 2013, I get "No symbols loaded". So I think I have to adress the problem from this standpoint.

-Ingvar

"Hi Gary, the title of this topic is:
My home made Extension won't show up in Vegas 14"

Yes, I saw the title.  My point was simply that Vegas v14 may still follow some caompatibility with prior versions, and work with extensions in the same folders.

Fair enough, Gary.  But i have tried to put those DLLs everywhere, the old folder structure, the one descriped oin Vegas 14 Help, the suggested folders in this thread. Doesn't work.

Now, is anyone heree really making extensions for Vegas 14? If someone would be so kind to chime in..

-Ingvar

Now, is anyone heree really making extensions for Vegas 14? If someone would be so kind to chime in..

-Ingvar

I believe a couple have chimed in.

Ok, for those who compile extensions for vegas 14, I have these questions:

1. What version of Visual Studio do you use? I use VS 2013
2. What .Net version does your extesion use? I have tried 4.0 and upwards
3. What DLLs in the VEgas 14 directory do you reference? I reference  ScriptPortal.Vegas.dll
4. Can you set breakpoints in the main unit, who are hit, when running Vegas 14 and debugging from Visual Studio?
5. Is this folder described in the Vegas 14 help wrong?  C:\Users\user name\AppData\Local\Vegas\ Application Extensions
6. Can you help me out by showing the source code for a basic extension that works?

Here is my code which works (you get a menu item, nothing more) in previous versions og Vegas, but not in Vegas 14. The only change is that ScriptPortal has replaced Sony:

using System;
using System.Collections;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Windows.Forms;

namespace VegasTest
{
    public class VegasSubTitler : ScriptPortal.Vegas.ICustomCommandModule
    {
        private string EXTENSION_NAME = "Vegas Extension Test";//

        public void InitializeModule(ScriptPortal.Vegas.Vegas vegas)
        {
        }

        ScriptPortal.Vegas.CustomCommand customCommand = new ScriptPortal.Vegas.CustomCommand(ScriptPortal.Vegas.CommandCategory.View, "VegasExtensionTest");
        
        public ICollection GetCustomCommands()
        {
            customCommand.DisplayName = EXTENSION_NAME;
            customCommand.Invoked += this.HandleInvoked;
            customCommand.MenuPopup += this.HandleMenuPopup;
            return new ScriptPortal.Vegas.CustomCommand[] { customCommand };
        }

        void HandleInvoked(Object sender, EventArgs args)
        {
            try
            {
            }
            catch (Exception E)
            {
            }
        }
        
        void HandleMenuPopup(Object sender, EventArgs args)
        {
        }
    }
}
 

altarvic,
thanks a lot! I will investigate and come back later today!
-Ingvar

Ok, I found out about it! And I will sum it up here:

You can put your extensions in these folders:

1. C:\ProgramData\VEGAS Pro\Application Extensions
2. C:\Users\my_user_name\Documents\Vegas Application Extensions

The folder described in the help file, does not work, as others have pointed out here.
So why didn't my extension work for Vegas 14, even when putting it in the folder (1) altarvic suggested? The answer is, I had Vegas 13 extensions with the same namespace in folder (2). So vegas 14 tries to load them, then stumbles across the now deprected name "Sony" and fails to load the assembly with the same name from folder (1), even if it has replaced Sony by ScriptPortal.

Now everything works. I can use either folder 1 or folder 2. I just have to rename the assembly name, as altarvic has adviced me to do. Thank you all for your help, and not the least for your patience!

-Ingvar