AX2012 - C# 项目中的 .Net 程序集未在 AOS 上更新
我们已将在开发环境中开发的 AX2012 模型部署到生产环境中。
该模型由一个 C# 项目组成，其设置设置为部署到客户端和服务器。
部署后，似乎为客户端 vsassemblies 文件夹（在 c:\user\appdata\microsoft... 下）生成了 C# 项目的 .NET 程序集，但它不会在 C:\program 下的 AOS 服务器上生成files\Dynamics AX...\Server\bin\Vsassemblies 文件夹”。
热插拔设置已打开。有办法强制重新生成吗？即使重新启动 AOS 服务也无法重新创建程序集。
We have deployed a AX2012 model that we developed in our dev environment into a production environment.
The model consists of a C# project, for which the settings are set to deploy to client and server.
After deployment it seems that the .NET assembly for the C# project is generated for the client vsassemblies folder (under c:\user\appdata\microsoft....) but it doesn't generate on the AOS server under C:\program files\Dynamics AX...\Server\bin\Vsassemblies folder".
The hot swapping setting is on. Is there a way to force the regeneration? Even restarting the AOS service doesn't recreate the assembly.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
应该是这样的：
http://msdn.microsoft.com/en-us/library/gg889192.aspx
“在以下情况下，程序集将复制到客户端：
当从客户端调用程序集中包含的托管代码时。
当您访问 IntelliSense（在设计时）时。
当您编译以下代码时：引用托管代码程序集。”
另外，有迹象表明某些文档可能不正确，以及一些关于服务器位的讨论：
http://daxmusings.blogspot.com/2011/09 /ax-2012-net-assemble-deployment.html
should be something like this:
http://msdn.microsoft.com/en-us/library/gg889192.aspx
"An assembly is copied to the client under these circumstances:
When a call is made from the client to managed code that is contained in the assembly.
When you access IntelliSense (at design time).
When you compile code that references the managed code assembly."
also, there are indications some of the documentation may be incorrect, and a bit of discussion about the server bit:
http://daxmusings.blogspot.com/2011/09/ax-2012-net-assembly-deployment.html
我们在 Microsoft Dynamics AX 2012 中的 .Net 项目中遇到了相同的问题和许多其他问题。
您是否使用 Microsoft Team Foundation Server 2010 并尝试签入和签出这些项目？解决方案文件将具有写入锁定，有时无法找到在 Visual Studio 中打开它的项目...等等...
我认为 Microsoft Dynamics AX 的开发团队有很多工作。啊...我忘记了...尝试重命名已签入的 AOT 元素。首先，一切看起来都不错。但如果其他开发人员得到最新的更改。 “已经有一个带有 origin id 的对象”...太棒了...:-/
管理一个拥有超过 10 名开发人员和许多问题的团队确实很困难。
We´ve got the same and many other Problems with .Net Projects in Microsoft Dynamics AX 2012.
Do you use Microsoft Team Foundation Server 2010 and tried to check in and check out those Projects? The Solution Files will have a write lock, sometimes it can´t find the project to open it in Visual Studio... and so on...
I think the Developer Team from Microsoft Dynamics AX have a lot of work. Ah... I forget... Try to rename an already checked in AOT element. First it all looks good. But if another developer get latest changes. "There is already an object with origin id"... Great... :-/
It is really hard to manage a team with greater than 10 developers and many many problems.