Comments
Sort by recent activity
I can repro it here by creating a project with a few references, saving it, closing SA, deleting a referenced assembly and opening the project file by double clicking it. / comments
I can repro it here by creating a project with a few references, saving it, closing SA, deleting a referenced assembly and opening the project file by double clicking it.
Sure, I will give it a try, but for now it wont solve my problem with the reports from the other machine. / comments
Sure, I will give it a try, but for now it wont solve my problem with the reports from the other machine.
I had upgraded the old machine to 5.5, which is whats running on the new one too.
Though I did copy the files to the location of the existing database on the new machine, which was %programdata%... and no longer in programfiles. / comments
I had upgraded the old machine to 5.5, which is whats running on the new one too.
Though I did copy the files to the location of the existing database on the new machine, which was %programdata%......
I have the feeling that exception reports needs some rethinking how it works. It is really targeted to single-machine scenarios, with no recovery or backup functionality, though I am tempted to try using SQL as backend, which seems to offer a bit more freedom. / comments
I have the feeling that exception reports needs some rethinking how it works. It is really targeted to single-machine scenarios, with no recovery or backup functionality, though I am tempted to try...
Trying that now. But first: the %programdata%\red gate\smartassembly folder on my old machine is empty, all the files are instead in the program installation folder. This was a default installation, the maps path was never changed. This might be the result of upgrading from previous versions.
Tried, and not really working. When I try to open the saved exception reports (*.saencryptedreport) I get either "The report is not present in the selected database" followed by an exception or I get "The report is not associated with an valid project ID".
I didnt yet get any new reports to download, lets see how that will work out. / comments
Trying that now. But first: the %programdata%\red gate\smartassembly folder on my old machine is empty, all the files are instead in the program installation folder. This was a default installation...
Yes, the second build fixes it. Wondering why it doesnt fix it in the first run already? / comments
Yes, the second build fixes it. Wondering why it doesnt fix it in the first run already?
When I remove those references and build it on the commandline, the assembly seems to work just the same and there are no build errors either. So my guess is that those "new" *smartassembly* references are not absolutely needed. / comments
When I remove those references and build it on the commandline, the assembly seems to work just the same and there are no build errors either. So my guess is that those "new" *smartassembly* refere...
I DO use automatic reporting but no SDK at all. Just tested it and it seems to add them only when using the error reporting feature.
Though old projects without those references seem to work the same. So do we need them :? ?? / comments
I DO use automatic reporting but no SDK at all. Just tested it and it seems to add them only when using the error reporting feature.
Though old projects without those references seem to work the sa...
Another thing that comes to mind now is the HintPath. A project specific HintPATH would be great instead of a assembly specific reference.
Something like
<SearchPath>$(ProjectDir)/References</SearchPath>
would be just great to find assemblies used in the current project without specifying each one with full path. / comments
Another thing that comes to mind now is the HintPath. A project specific HintPATH would be great instead of a assembly specific reference.
Something like
<SearchPath>$(ProjectDir)/Ref...
Oh yes and PLEASE: make the GUI remember and use paths already selected to resolve references. Nothing more annoying than having to select 10 times a folder for 10 assemblies which are in the same folder. Argh. :x / comments
Oh yes and PLEASE: make the GUI remember and use paths already selected to resolve references. Nothing more annoying than having to select 10 times a folder for 10 assemblies which are in the same ...