In BizTalk 2006 R2, is there some way to regenerate the reference to a WCF service that has been created using the "Add Generated Items / Consume WCF Service" option?
I tried just re-running the wizard, but it creates new ODX, BindingInfo, etc. files, and breaks the solution, so that's not the way :-(
Searched the web, but not found any references to how to update the references, just plenty on creating from scratch
I agree with Marvin, delete the old files and generate new ones.
If you keep the old ones before you regenerate you will of course have other names on the newly created, like yourname1.odx if you choose the same name as before (yourname), and breaking the solution that way, since the type name will be different.
Related
I am working on a VSTO-Excel-Addin (VB.NET) that we are about to sell to different companies.
The addin will (hopefully) be used by a couple of users of each customer. We are using ClickOnce for a web-based deployment.
The addin provides some default-settings - that is no problem with the app.config. User-specific Settings are also working fine with ClickOnce.
However what makes quite some headache is how to store settings per customer. Database-connectionstrings for example cannot be stored on the application-level but it would also be painfull for all users to change the Connection-string manually. What I would imagine is another layer (per Company) where this sort of Setting can be stored.
One alternative would be to create one VSTO-Project per customer but this would bring a lot of disadvantages since we are updating the addin quite regularly.
I would be happy about any ideas!
Regards,
Julian
I would show Excel's built in connection properties dialog and let each client configure this themselves.
You really shouldn't be distributing connection strings for all your clients as part of a shared package. It'll be a maintenance nightmare.
http://office.microsoft.com/en-nz/excel-help/connection-properties-HA010175443.aspx
What about storing the settings as custom properties in Book.xltx and copy it to
C:\Users\username\AppData\Roaming\Microsoft\Excel\XLSTART
This is how you can programatically read and create Custom Properties in Excel.
When a new workbook is created then all the properties from Book.xltx will be available for New Workbook as well. But this solution may not work if the existing workbooks are opened so yo might have to explicitly add these properties when any existing workbooks are opened using the above solution.
Ok, I think I understand the problem. :)
How about storing all the settings in an offsite database that you maintain and using a webservice to allow the settings to be read and set and giving each client a unique license number that would allow them to access this webservice.
That way the individual users would only need a license number to set it up.
I have have a solution that I created with the new modeler tools. This gave me
two full "endpoints" in a single solution.
Now when I run them through my automated build, I have two dlls in the same
folder that implement IConfigureThisEndpoint.
If I just run NServiceBus.Host.exe \install (to get a Windows Service), it gives
me the (expected) error that there is more than one class that can be used.
I did some searching and Udi states here:
http://tech.groups.yahoo.com/group/nservicebus/message/3937 that "You can
specify which class you want loaded and avoid these issues - as the server
project in the pub/sub sample shows".
I looked at the pub/sub sample and I can't see how I can specify my class (at
least not at the command line).
Is there a way to get around having to modify my build to put the files in
separate folders? (Not really an easy task for me.)
Add a config entry to your app settings with the key EndpointConfigurationType and the value being the assembly qualified name of the type.
We have a Visual Studio solution that comprises multiple production and test projects. The solution uses several web services.
The way things are organized at the moment, each project that needs access to a web service has a "Service Reference" for that web service added to it. This means that there are multiple (usually only two) references to every web service: one in the production code, one in the test code.
However, we are finding a problem: when the other web-services get updated, we often forget to update ALL the service references to them (usually in the test projects that use them).
Someone suggested that we add a new project to the solution that contains ALL the service references and that NO OTHER project should have a service reference included.
Are there any "gotchas" with this proposed approach?
Is it a good idea? And why (not)?
We use the same approach as well, however there's a very inconvenient gotcha - you can't have multiple service-references from the same application.
So we ended up having to create the service-references manually using the svcutil, but other than that, we're pretty happy with the change.
I have made a ContentType in Visual Studio 2010 for my SharePoint 2010 project and the first time I deployed the wsp through the WSPBuilder there were no troubles but now every time I try to deploy, it keeps saying that it can't activate features because "The field with ID {insert random guid here} defined in feature {60938308-3563-497c-bc55-b2ae847ca8b8} (the feature activating my contenttype on the site) was found in a current site collection or in a subsite."
The contenttype and site columns gets created on the rootweb and even though I try to either deactivate the feature or completely uninstall it, the site columns and contenttype won't be deleted from the ContentType gallery or Site Columns gallery.
How can this be?
I use pure feature and XML functionality. No eventreceivers are involved.
SharePoint will not let you delete site columns and content types that are in use. This makes the upgrade process a little tricky.
If you just want to add a field to your content type you can use the Feature upgrade facilities in SharePoint 2010. This blog post series should help you: http://www.sharepointnutsandbolts.com/2010/06/feature-upgrade-part-1-fundamentals.html
If you need to make any other changes (remove field, change type, etc) then you need to take a different approach. You'll create a new content type that inherits from, and eventually replaces, your existing content type. This strategy is discussed here: http://msdn.microsoft.com/en-us/library/aa543504.aspx
Besides checking out what Rob suggests:
Did you install Visual Studio SP1?
I received that error before installing SP1 and the workaround was closing all Visual Studio instances and starting it up again. After starting up deployment was possible again.
Is it possible to update a Domain Service?
Right now I delete the service and add again its stupid.
There's no update support in the UI, but if you're just returning whole entities there should be no reason to regenerate, everything should just flow through when you update the edmx and rebuild the project (to re-run codegen for the client).
Just for information if anyone else stumbles upon this thread in desperation (like I just did) ...
I updated my edmx model in a Silverlight application, having only renamed one database column and added a couple of foreign keys, and the Client project immediately started generating 30+ fatal errors, all due to the fact that, despite the Web project building "successfully", it did not generate the app.g.vb "generated code file" for the client, resulting in "WebContext not defined", missing ApplicationResources etc etc.
The first time this happened I just gave up, deleted the edmx file and the domain service and started again.
The second time it happened I got angry, but this time I just deleted and re-created the domain service, and everything went back to normal.
So it looks like there are definitely some modifications you can't make to the edmx model without requiring re-creation of the Domain Service.
Ade.