In vsix-package extension for SSMS I have problem -
after the Initialize function the value of the sub-key is deleted (in the registery edit) and it causes that if I open the SSMS several times in a row, the extension is loaded only to the first instance of the SSMS.
I know the deleting happens between the function Initialize and the event DTEEvents_OnStartupComplete
What can I do in order to prevent the deleting or when is the value deleted?
Thank you
You need to have your extension whitelisted, all other extensions will not run under SSMS
Related
I am usung TYPO3 V11.5.3 and figured out, that some pages not working anymore. The reason was, that in the database of the extension, in some entries the delete flag have been set.
If I set this values back to 0 with phpmyadmin, the next day these values are again set to 1 and the web pages are not working.
What's going on there?
How can I avoid it, that TYPO3 sets again these values?
Edit
Rudi, this extension has worked for about 1 year without any problem.
The extension has 3 databases, Album, Discs and Tracks. A album has one or more discs and a number of tracks. The extion is collecting this information (BE) and displays it (FE).
Can it be, that TYPO3 is automatically setting back the changes I have made with phpmyadmin?
** EDIT **
I tried several things, but they didn't solved theproblem!
Finally, I deleted the effected tables and but them new. These seems to solve the problem.
Finally I figured out was the problem was.
I generated my extension via extension_builder. And extension-builder created a list view for the frontend, which I didn't use, but also not deleted. This list view was found by GOOGLE and executed the delete function of this list view!
I'm using MySQL Workbench and I am trying to create a routine. However, At the time of creating routine some error comes,then i deleted that routine. Now I synchronize the model with the existing database, the Routine group error is coming, though i remove that routine group. Can anyone help me how to remove this error from Model?
The _SYNTAX_ERROR suffix is added by MySQL Workbench to indicate that it found a syntax error in your routine code. Once you fixed that the name will change back to what you gave it. And then you can also synchronize your model.
I faced the same issue, cause i copy&pasted some c# code into a routine group, and it immediately became invisible by workbench. Synchronization now always reporte errors, even after deleting the whole routine group. The faulty code was stuck somewhere, inaccessible through the Workbench UI.
Just found a solution atm:
Do a regular synchronization and tell Workbench to change the sync-direction on the error entries. This will remove the faulty lines of code, even if they are not accessible through the Workbench UI.
Is there a way to customize and save publishing scripts in a Database project?
If I want to modify some columns and this might incur data loss, or the other way around I want to populate columns in order to be able to modify the column type (to not null) how can I do that with SSDT in visual Studio 2013?
Modify Columns w/ possible data loss - you'll need to enable the option when publishing to allow possible data loss or that won't be run.
Populate columns to modify - best way would be a pre-deploy script, probably checking to make sure that there are NULL values to update before doing the update. You'll need to add a script of type pre-deploy if one doesn't already exist, then either drop your code straight in that script or create a new script of type "not in build" and include that file in the pre-deploy script.
http://schottsql.blogspot.com/2012/11/ssdt-pre-and-post-deploy-scripts.html
I am using Light switch on Azure.
After I modified a column in a record when I click the Save button I got
"Store update, insert, or delete statement affected an unexpected number of rows(0). Entties may have been modified or deleted since entities were loaded, Refresh ObjectStateManager entries.
I use VS 2012 on my dev machine debug this light switch app. it works fine and no errors when I modify the save column on same records then save it.
Is anybody in this forum has idea what could cause this? and how should I work around it?
I suspect the azure machine don't have the same version of EF with my dev machine. but in the Light switch project both client and server reference I could not find the EF is referenced there. So I don't know how I can bring the EF dll on my machine up to Azure machine.
Anybody could give me some suggestion on this?
Thanks
Chris
Usually it's a side effect of Optimistic Concurrency. This article can give you the idea of it in Lightswitch:
LightSwitch 2012 Concurrency Enhancements
When it's working on dev machine and it's not working on Azure, I guess something is not right in your production database.
you can also take a look at Entity framework: affected an unexpected number of rows(0)
Having Instead of insert/update triggers, sometimes SQL server does not report back an IdentityScope for each new inserted/updated row. Therefore EF can not realize the number of affected rows.
Normally, any insert/update into a table with identity column are immediately followed by a select of the scope_identity() to populate the associated value in the Entity Framework. The instead of trigger causes this second step to be missed, which leads to the 0 rows inserted error.
You can change your trigger to be either before or after insert or tweak your trigger by adding following line at the end of it:
select [Id] from [dbo].[TableXXX] where ##ROWCOUNT > 0 and [Id] = scope_identity()
Find more details in this or this thread.
Recently we added a "audit_logs" table to the database, and after some frustration I realised that there was already an "auditlog" table in the database for some reason. It wasn't being used so I dropped it. I deleted the Auditlog.pm and AuditLogs.pm files from my schema, and then regenerated. For some reason DCSL again created AuditLogs.pm for the "audit_logs" table, even though there was no longer an "auditlog" table or Auditlog.pm file that would conflict with it.
I have tried just about everything I can think of to get it to generate Log.pm without success. The only thing that I can figure is that it is caching the moniker map somewhere, and I cannot seem to reset it.
I eventually tracked this problem down to an issue with the Lingua inflector. It was picking up "logs" as a singular verb instead of a plural noun. This happened because it followed the word "audit" which ends with "it." Basically, I had to write a custom moniker_map function that added an exception for audit_logs.