I may not have thought of this as an option without the prior suggestions to spark this idea. Thanks the other commenters for their suggestions.
Whether you work from the local or the remote, the changes persist and are shared on each machine. recommends 256kbit/s per TM1 session and our WAN connection available bandwidth fits this requirement. As we checked, they have enough bandwidth to access the service. Our users accessing TM1 web over WAN links reported that using TM1 is very slow. Note that this configuration must be reverted when debugging is complete. After a restart, the Windows machine uses that information to log on to mydomain.
Where 1.2.3.4 is the IP address of the domain controller named dcnetbiosname in the mydomain domain. Instead, this alternative will let you host a project/workspace/notes.etc on your local machine, start a live-share session, then join that live share session from the remote. We have the following problem when using TM1. Simply include a line: 1.2.3.4 dcnetbiosname PRE DOM:mydomai. Like other suggestions, this isn't going to let you copy/paste from one machine to another, but in a way, it allows for much more. The extension is Live Share and it works flawlessly (at least on my machine 😉) This service runs as an extension with several products, but for developers, this would likely be their IDE and code editor: Visual Studio and VS Code.
This same service is what's used behind the scenes to power what Microsoft refers to as "Live Code Sharing". Microsoft developed a "Relay Service" called Azure Relay. The earlier suggestions and "work-arounds" were useful, but in 2020, there is a better way :)
0 kommentar(er)
