Ok so in the LIVE instance of AX - I go to the AOT, find my report, right click edit. This then launches VS and I can edit the report. However in the TEST environment I cannot do the same. " Unable to connect to the AOS specified in the Microsoft Dynamics AX Client Configuration".
How to I point the TEST environment to VS? I've checked the config file but nothing obvious there.
Thanks in advance.
See how to Open Visual Studio with a Specific Configuration.
If you are working with reports, the Visual Studio integration uses the active local client configuration to establish the connection. Examples that require a Reporting Services configuration include deploying a report or selecting a query as a data source. To point to the correct AOS in this scenario, create a copy of the configuration file in the Visual Studio integration folder.
In order to start VS for a specific change the VS shortcut target to point to correct configuration:
"C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe" /AxConfig ContosoDev
or
"C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe" /AxConfig z:\Config\ContosoDev.axc
This will not work from the AOT of cause, VS will then use the current configuration.
You could have a look here. It has to do with using the default configuration instead of the AXC file.
There is a KB, although it may not be for your version, you can apply the technique used:
KB 2827469 Visual Studio .NET launched from within AOT overlooks
AxConfig parameter and any custom config profile. When open VS
Project from AOT SysVSProjectsExport/EditProject() method executes and
it calls the below VSModeling framework Edit method where it is
passing only the selected solution to the devenv.exe file. But since
the current AXClient instance is opened from a saved configuration
file, we have to pass that configuration file to devenv.exe as a
switch "/AxConfig". As this /AxConfig switch is not considered Visual
Studio default considering active AxClient configuration from system
registry.
So:
Try to open AX from the default configuration and avoid to use the
AXC file. Then, try to edit a VS Project from AOT.
Related
I'm working on SpecFlow tests in Visual Studio 2019. The designer file (.cs) doesn't get generated when the feature file is added.
Works on other machines with similar configuration and nuget packages.
The designer file should be generated automatically.
This is probably happening, because the generation of the code-behind file on saving is not enabled.
In the latest update of the VS Extension of SpecFlow we changed the default to false. The reason for it was, that it is a legacy function and you should switch to MSBuild Generation of the code-behind files.
Documentation for it: https://specflow.org/documentation/Generate-Tests-from-MsBuild/
To enable the feature again, you have to go to the options:
Full disclosure: I am one of the developer of SpecFlow.
I have migrated a MVC4 web application version controlled in VSS 2005 to TFS 2015 and that migration is successful.
Then I tried to open the project in VS 2010 (Since VS2015 does not support)
It gives me following error. How do I connect to TFS successfully
Error message:
The solution appears to be under source control, but its binding
information cannot be found. It is possible that the MSSCCPRJ.SCC file
or another item that holds the source control settings for the
solution, has been deleted. Because it is not possible to recover this
missing information automatically, the projects whose bindings are
missing will be treated as not under source control.
Using:
Windows server 2012 + Updates
SQL 2014
TFS 2015 (Version 14.0.24712.0)
Open file - Source Control - Change Source Control... Select all projects and click the Bind... button. That should re-create the binding, if the files are in a valid TFS workspace.
Since you're mixing and matching VS2010 and VS2015, you may first need to set your workspace to "Server" instead of the default for 2015's "Local". VS2010 doesn't support local workspaces. You can change this setting from Visual Studio 2015 only.
In VS 2010, or VS 2012, you can pick a "Solution Configuration", that has been custom defined, that can define local variables used with the #if #elif #endif syntax to change your code dynamically through that drop down. Also in that configuration, you can choose whether it's built or deployed, platform you're targeting, and the local configuration you want to use per project.
When you choose a configuration, then close Visual Studio, and re-open Visual Studio, it remembers what configuration you chose, what I can't seem to figure out, is where it saves/stores that configuration information, and I need to automate it.
Does anyone know of either:
A way to use the command line compiler to automate solution level builds using solution configurations
Where Visual Studio stores the currently selected configuration information
Or, ideally, both?
Visual Studio actually stores a solution's build configuration selections in the solution file itself. Even though the "*.suo" file is not checked into version control, the solution's build configuration selections will propagate to other machines that are sync'ed to the same version control system.
If you open a "*.sln" file, you will see a section called "GlobalSection(ProjectConfigurationPlatforms)". If a project is not checked for build or deploy, you will see something like this:
{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}.Debug|Mixed Platforms.Build.0 = Debug|Any CPU
{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}.Debug|Mixed Platforms.Deploy.0 = Debug|Any CPU
The ".0" strings indicate that the the build and deploy are unchecked.
A way to use the command line compiler to automate solution level builds using solution configurations
msbuild.exe /p:Configuration="Solution Config" /p:Platform="Solution Platform"
For example, you can do:
msbuild.exe /p:Configuration="Release" YourSolution.sln
To build the "Release" configuration.
Where Visual Studio stores the currently selected configuration information
This is stored in the user's .suo file, next to the .sln (solution) file.
I am attempting to create a custom connection manager for performing SFTP operations from within SSIS. I have completed implementation, strong-named my assembly and installed it in both the GAC and the C:\Program Files\Microsoft SQL Server\90\DTS\Connections folder. The problem is that the "Add SSIS Connection Manager" dialog doesn't show my new connection type and I'm at a loss as to how to diagnose this issue. So far I have ensured that Everyone has Full Control to the C:\Program Files\Microsoft SQL Server\90\DTS\Connections folder.
Possibly related to this issue is that I cannot see the assembly when I browse the GAC, even though the gacutil program reports success when I run it to add the assembly.
What steps could I follow to diagnose the root cause of this issue? Is there anything else that I need to check to make it possible to add a add a custom connection manager?
EDIT: I should also note that the custom connection manager is compiled using .NET 4.0. This is why I cannot see the assembly in the GAC after installing it I believe, as the assembly is being placed in the %WINDIR%\Microsoft.NET\assembly folder rather than the %WINDIR%\assembly folder. I am using .NET 4.0 because of this issue.
EDIT #2: It turns out that if I create my custom connection manager in a Visual Studio 2008 project, compiled against .NET 3.5 then everything works fine. (Apparently using Visual Studio 2008 is a workaround for the version issue linked above.) So the real question now is why the SSIS Designer doesn't pick up .NET 4.0 custom tasks and connection managers.
Did you add it to the toolbox? The doco has this as a mandatory step.
Also, you must close and reopen SSIS Designer after you install a new or new version of a custom object.
You could also try resetting the toolbox.
I'm facing quite a problem while setting up automated TFS Builds. Basically I created new configuration called Tests, added transform config, defined different connection strings for the Database. Then defined TFS build, building whole solution with MSBuild arguments /p:DeployOnBuild=True /p:Configuration=Tests.
The problem is that in the drop location (Build_PublishedWebsites\Project) I get web.config, web.debug.config, web.release.config and web.tests.config, however I would expect just one transformed web.config.
I already checked PDC presentation Web Deployment Painkillers: Microsoft Visual Studio 2010 & MS Deploy but didn't help.
Thanks for any answer.
Web.config transforms are part of the new Web Publishing Pipeline (WPP) in Visual Studio 2010.
During the build process the "CopyWebApplication" target is executed to copy the website to the _Websites folder on the build output directory. Due to backwards compatibility reasons, MSBuild uses the "old" (VS2008) copy behavior by default and not the new WPP system.
To opt-in to using WPP, set the following MSBuild properties:
/p:UseWPP_CopyWebApplication=True
/p:PipelineDependsOnBuild=False