microsoft
Transforms for Connection Strings ignored by XSD queries
Using VS 2015, Application in test still uses the connection string for debug even though the previewed transform is showing the proper connection string for the test environment. After moving the queries out of the xsd designer and doing them in code, the application connects to the proper database. Essentially, XSD based queries ignore the slowcheetah transform.
Is this a web application? When running C# web projects via f5, the web.config from your source is used directly and not the transformed web.config SlowCheetah puts in the output directly.
I don't get why you closed the other issue. Is it by design that ApplicationSettings Transforms are ignored also in a Windows Forms Application?
@dlee1964 I believe this issue and #69 are the same. I would like to point out slow-cheetah is not the correct place for XDT/XSD issues. Slow-cheetah uses XDT, but does not own it. You can find XDT help here. That is not to say this isn't a slow-cheetah issue though, it could be the transform is not being applied at all by slow-cheetah.
Can you verify if your file is being transformed? Do some parts of the transform get applied? Does previewing the transform work? If preview shows the correct transformation, but on build it is different, then it is an issue with slow-cheetah or another build step undoing what slow-cheetah did.
If you can verify the transform is being applied, then most likely your transform file is incorrect. In which case I recommend reading the help page I linked earlier. One idea off the top of my head is maybe an xml namespace issue in your transform file? If the elements you are transforming come from a namespace you need to fully qualify it in the transform file.
No, Issue #69 is not the same at all. Not even close. Please re-read it and re-open it.
Yes, the preview showed that the transforms were correct. I was getting no error on the transform. The same connection string was to be used for XSD and non-XSD based queries. They were each hitting different databases, yet there was only one connection string in the app.config. So, I know the transform was correct because the non-XSD queries were hitting the correct database while the XSD based queries weren't.
@dlee1964 as far as it concerns slow-cheetah, these are the same issue. The differences between them are in areas slow-cheetah is not responsible for. The issue is with the project system you are using, with XSD itself, or with the way you wrote the transform. Slow-cheetah is not responsible for any of those issues.
First, was the resulting file in your output directory correct after a build? Was the transform applied to it? If so, then the issue is with the project system is my guess. Maybe it does not read the file from the output directory during testing, it could be using the un-transformed file directly from your source tree.
As I have been in active development and up against a deadline, I had to work around the issues and thus change things significantly, so I cannot answer the questions with confidence at the moment. I will have to create a small test project to duplicate the issues again to answer your questions. As I have already stated that the coded queries were using the correct transform and the XSD queries were not (within the same project), I suspect the output file was correct and the XSD was ignoring it. In any case I will create the small project to demonstrate both issues and perhaps I could upload it for you to review at some point.