Community
Showing results for 
Search instead for 
Do you mean 
Reply

Can't debug with Visual Studio: "Debugging Not Allowed"

Highlighted
New Member
Posts: 13
Country: USA

Can't debug with Visual Studio: "Debugging Not Allowed"

[ Edited ]

I used to be able to debug add-ons with Visual Studio. I'm now getting the following error when it starts Act:

 

---------------------------
Debugging Not Allowed
---------------------------
This software is protected to provide copy protection and cannot be debugged. Please restart the application.
---------------------------
OK
---------------------------

 

The version I'm using is: Act! Premium Version 21.0.295.0, Update 7

Highlighted
Bronze Super Contributor
Posts: 1,284
Country: USA

Re: Can't debug with Visual Studio: "Debugging Not Allowed"

What is your .NET framework target?

 

Try using 4.0

 

-- Jim 

Highlighted
New Member
Posts: 13
Country: USA

Re: Can't debug with Visual Studio: "Debugging Not Allowed"


@jimdurkin wrote:

What is your .NET framework target?

 

Try using 4.0

 

-- Jim 


4.7.2. Would it need to be downgraded?

Highlighted
Bronze Super Contributor
Posts: 1,284
Country: USA

Re: Can't debug with Visual Studio: "Debugging Not Allowed"

I always set the framework to 4.0 and compile against ACT 16.0.291.

This way Impact Suite maintains backward compatibility.

 

Jim

 

Highlighted
New Member
Posts: 13
Country: USA

Re: Can't debug with Visual Studio: "Debugging Not Allowed"

[ Edited ]

Unfortunately I'm only able to compile with version 21, which I think is why it's using .NET 4.7. Is debugging not possible in later versions? How are add-ons supposed to be created if not?

Highlighted
Bronze Super Contributor
Posts: 1,284
Country: USA

Re: Can't debug with Visual Studio: "Debugging Not Allowed"

I remember other developers having issues with the new DLLs. Maybe on of them can chime in here?

 

In the short term, compile against v16. In general you can have a .Net 4.x project reference any dlls even if they were compiled against older versions of .Net/Act.  Act does have a <bindingRedirect> in the configuration which allows your addon compiled against an older DLL to redirect to the newer DLL installed on the target PC.

 

Act should have created the binding redirect entry during installation in the .NET config file.

C:\Windows\Microsoft.NET\Framework\v4.0.30319\config\machine.config 

 

<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="Act.Data" publicKeyToken="ebf6b2ff4d0a08aa" />
        <bindingRedirect oldVersion="7.0.0.0-22.999.999.999" newVersion="22.0.205.0" />
      </dependentAssembly>
    </assemblyBinding>

There will be a binding entry for every Act DLL.  If you do not have the <bindingRedirect> try running the MachineConfigUpdate.exe in the root act folder or reinstall Act.

 

Hope this helps

-- Jim 

Highlighted
New Member
Posts: 1
Country: USA

Re: Can't debug with Visual Studio: "Debugging Not Allowed"

You must specify an application object when running from within Visual Basic McDVOICE.