My worker role will not run and is constantly recycling. I get a filenotfoundexception which points me in the direction of missing assemblies. All works fine locally of course.
I've gone through the references for the worker role project and made sure that copy local is true where necessary. By RDP'ing to the VM I can see that when I deploy my worker role several of my solution's project dlls (like my entity and data dlls) are missing and are not in the package. I don't understand why they would be missing. They are compiled for .Net 4, "any cpu" and copy local is true. What am I missing?
Thanks
Matt
this happens if your roles reference one another. For example, I had a worker role and a web role in my azure project. The webrole was referencing the worker role. As soon as I moved the reference the packaging worked correctly.
I didn't get to the bottom of this but what I did do that solved it was to create another worker role. I did also noticed that I hadn't included the app.config with copy always set correctly which was a different problem but worth noting for others finding this.
Related
I have a BizTalk 2013 application comprising of 3 projects - orchestration, schemas and maps.
In my orchestations project I have references to my maps and schemas projects within the same application.
However, when I try to select a map or schema using the referenced assemblies nothing is showing, not even the standard dll's such as System.XML or System.Configuration, the only thing I can see is Microsoft.XLANGs.BaseTypes.
I can see the references in the solution explorer but not when I try to use them in anywhere in the orchestration.
I had this problem before but can't remember how I resolved it, any suggestions?
I ran into the same issue today. The only reference I was seeing was the XLANG.BaseTypes.
Turned out I set build action to none one time when I needed to test something and didn't need this orchestration. Setting it back to BtsCompile fixed it.
After deleting and re-creating the entire project which I seemed not to be able to reference everything is building and referencing as normal. Not sure what caused it in the 1st place though, so still open to suggestions for that.
thanks
Some background to my problem...
We are currently using ClickOnce to deploy part of our solution which was working a treat until we encountered a scenario where we are now required to have multiple instances of our application installed on the same PC. We are able to achieve this internally and have this working perfectly as we know what instances we have so our build process will update AssemblyName to include the instance name before publishing the installer, this means we are able to have multiple instances on our PCs internally (ie, test, live and demo etc).
Our external deployment process is slightly different, we take one of the ClickOnce installers created in our build (along with all our other components that make up our application) and as the ClickOnce installer is deployed on a server we update the app.config along with the manifest files and resign so they now have client specific details. If a client chooses to have multiple instances of our product installed the ClickOnce will now fail when a second instance is installed on a desktop PC as all instances share the same assemble name.
So finally to the question, does anyone know of a way to update the manifest etc after the clickonce package has been created to allow multiple instances to be installed? We could go down the route of building many clickOnce installers but I dont think this will really work for us, is there perhaps an alternative to ClickOnce which provides a similar upgrade experience for non-admin users?
Hopefully someone will be able to share their experiences and help me resolve this.
Thanks in advance
Doug
I don't know of another technology that allows such a simple auto update process. So sticking with ClickOnce... I think this link might be useful. It explains what you need to do to have the same app installed twice. Essentially changing the assembly name and product name should do it.
Hope that helps.
Greg
I have a C# Visual Studio console application with a service reference. The company providing the service offers two API's one for test and one for live. They are supposed to be essentially the same service but with different URL's to different servers.
When I right click the service reference and choose Configure Service Reference, I am able to enter the the URL for the live service; and my project compiles properly.
I am new to this and am not really sure if I should be reconfiguring the service or if I should be deleting it and re-adding it in? I don't know if there are .config files I should be changing or cleaning manually.
So I guess my question is - are there pitfalls or better practices for this process that I should be aware of?
Any advice greatly appreciated. Thank you.
I have worked with Service References myself and so far never had any problem with just updating the service reference. If you like/need to change the configuration, it is possible by editing the .config file that gets generated
Sorry I'm just starting out with Azure, hopefully the following question makes sense.
I have an Azure project with 3 roles. I'd need to deploy one of them right now, but the other 2 roles are far from being ready and I'd have no use in deploying them at the moment (and that would also make me pay for 3 instances, right?)
Would Visual Studio let me deploy just the role I'm interested in?
If not, is there a way to temporarely remove the other roles without losing their settings?
(Thank you for your answer Richard, I was hoping I could — for example — just comment out parts of the ServiceDefinition / ServiceConfiguration files to tell VS not to package the extra roles.)
Just delete the projects you don't want to deploy from the 'roles' folder of your Cloud project, and they should be ignored.
You can easily add them back in when you're ready to use them.
I have a solution in Visual Studio that is comprised of 5 projects. The projects build to assemblies (.dll). I have the output path of each project set to \my-web-server\wwwroot\bin, which works fine on one project. In the properties for all of my projects, I have the output path set to the same directory, but when I try building all but one of the projects, I get the error:
Unable to copy file "obj\Release\Index.dll" to "\my-web-server\wwwroot\bin\Index.dll". Access to the path '\my-web-server\wwwroot\bin\Index.dll' is denied.
I assume it could be an issue with permissions, because my organization keeps things locked down, but I have no control over granting permissions. Any help in the right direction is much appreciated.
It must've been something silly. I deleted the .dll manually, then rebuilt. Looks like everything's working normally. Thanks.
The solution for me was to delete everything in bin and obj folders in every project. Just ran this powershell script as described here.
I had the same issue. A copy of Visual Studio (devenv.exe) was still running invisible in the background keeping the particular dll locked.
Delete all DLLs from the bin folder and build the solution.
just had the same issue, built a new project/solution, got it all working and then added to TFS.
Unfortunately I did not clean the build before adding and this meant some files that should not have been under source control were and were then read only(not checked out).
Manually deleting the files before rebuilding fixed the issue.
Most likely a program is running using that library.
This happens to me when running something to debug, and I forget to close it (not attached to IDE debugger).
And since this looks like a website, it is potentially due to the website being hosted from the development build folder, and someone is accessing it.
Similar to what Aequitarum said, it's mostly likely a locked file because it's in use. Since you have multiple projects, you mostly likely have references between them. And since you have all the projects outputting to the same folder any of the referenced projects will most likely get copied more than once if you have those files set to be deployed in the child project. (In a C# web application, you can view the properties of the reference and look at the "Copy Local" property.) And if you have the MsBuild project set to use multiple processors for the build, two child projects are both trying to copy the file at approximately the same time and one is erring out.
It's a very unique situation, but it is possible.
Working solution
Just go to Task Manager and search Detail (if its Win10) and search with your application name (for easy search just look at your windows user id wise)
And right click shows properties. just give the permission like Administrator access.
That's all its working fine for me. ( I was struggling for 1 week and its killed more my time)
It looks like WSearch Service locks up the files and does not release them. I disabled the service on WINDOWS 10 and was able to rebuild the solution.