Macros doesnt work anymore (visual studio c++)

Started by
5 comments, last by suliman 9 years, 7 months ago

Hi

My macros (typically prewritten strings of basic code such as forloops, sprint commands etc) doesnt do anything anymore. They run, but dont write the code.

Ive seen this commented on internet, people say remove some windows update etc (i have win7) but nothing works. Really annoying.

1. So any other way to fix it?

2. Any simple plugin that can write some prewritten code at the push of a keyboard shortcut?

Thanks!
Erik

Advertisement

It might help if you share a couple of examples of your macros so we can see what may be going wrong dude :)

BSc Computer Games Programming (De Montfort University) Graduate

Worked on Angry Birds Go! at Exient Ltd

Co-founder of Stormburst Studios

If you are talking about macros run by visual studio and not c/c++ preprocessor macros, they were removed from visual studio in
Vs 2013. There had been some talk from Microsoft about putting it back in in a future vs release.

"I can't believe I'm defending logic to a turing machine." - Kent Woolworth [Other Space]

I use visual studio 2008. After a certain point, all macros stopped working (the exact same macro used to work fine, i didnt change the actual macro). It thinks for half a second then nothing happens.

One of the macros (its more of a quick way of writing some common code really):


    Sub loop1()
        DTE.ActiveDocument.Selection.Text = "for(int i=0;i<10;i++)"
        DTE.ActiveDocument.Selection.NewLine()
    End Sub

You have to add some entries to a few config files. Which depends on the VS version. Looky here (http://visualstudioextensions.vlasovstudio.com/2014/02/13/visual-studio-2010-macros-stop-working-after-february-2014-windows-update/)

Fruny: Ftagn! Ia! Ia! std::time_put_byname! Mglui naflftagn std::codecvt eY'ha-nthlei!,char,mbstate_t>

You can try downloading and re-installing the Net Framework 4.0 Client Profile, Net Framework 3.5 and Net Framework 4.5.1 from Microsoft. The macros in VS 2008 depend on the net framework so if you uninstall one of those things, they may stop working and you won't know why. At least that's what happened to me once.

Yippieh!

Adding those lines of codes to the config files worked (when in admin mode).

Silly error.

Thanks guys!

E

This topic is closed to new replies.

Advertisement