In rare circumstances, you might have to change the value of this property.
The value of this property must be either blank or one of the built-in custom tools.
This design feature of Q-SYS ensures that all of the hardware pieces are quickly and easily kept synchronized with the same firmware version without having to individually update each piece.
NOTE: "Anti-virus software, installed on the computer with Q-SYS Designer, may have an impact on some of the Q-SYS Designer operations.
Copy the URL to a machine where you have access and copy the files down to some location then transfer the files to the computer with Designer.So I suspect that the 2 issues are related: the fact that VS doesn't think that the designer file is the same as the cs file (even though they are both partial classes and have the same name) and the fact that it can't compile because of a problem with the type (whatever that means). Does anyone know the criteria that VS uses to nest related files? Web sites in 2.0 don't let you specify a default namespace. However, the namespace for the designer, ascx, and files are all the same. Thanks, Steven Are you using the same project types all around? Net, the Web Site project that came originally with VS.Net 2005, and the new Web Application project, which is a port of the VS 2002/3 Web Applicaiton project and available in VS. Web Application projects nest files in the exact manner you describe.But I discovered that there’s a context menu item called “Run Custom Tool”.The most obvious choice is to select “Run Custom Tool” from the EDMX file, but that doesn’t do anything: If you F4 the corresponding T4 file you can see that the custom tool associated with the T4 file is: Text Templating File Generator So, I selected “Run Custom Tool” from the T4 context menu: And that generated the file: But I still didn’t have the Foo class in my object model: So I selected the “Run Custom Tool” on the “Conf Speakers. I will ping the product team to see if they can run the custom tool on the EDMX file when it is saved and recursively run on all the tt files associated with that EDMX parent.Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.