Using TFS 2013 I have several references that don't resolve. However, I can't see where you specify where these exist. Can someone tell me how I can get these to be resolved?
I have my xaml in a project. I didn't realize the references would be picked up from there, but evidently they are. I was able to get around my issue by adding a reference to the correct assembly in the project references area.
Related
After upgrading my cloud projects to Azure SDK 2.6. (via button in project properties window), everything works just fine, except I am getting like hundred of these warnings for *.cscfg files:
The complexType 'http://schemas.microsoft.com/ServiceHosting/2008/10/ServiceConfiguration:AccessControlElement' has already been declared.
The complexType 'http://schemas.microsoft.com/ServiceHosting/2008/10/ServiceConfiguration:AddressAssignmentsElement' has already been declared.
The complexType 'http://schemas.microsoft.com/ServiceHosting/2008/10/ServiceConfiguration:Certificate' has already been declared.
etc. for many more elements.
Already tried Clean, Rebuild, close-open VS... with no success. It doesnt affect functionality of the project, but it is really annoying to have Error list full of these things.
Any idea what is wrong and how to fix it?
OK, so guys from MSDN forums helped me solve this one.
Check SchemaVersion value in service definition file, it should be "schemaVersion="2015-04.2.6" (this one was OK for me)
Open service definition file as XML, right click on it, Properties -> Schemas. In the window (see pic), leave only ServiceDefinitionSchema26.xsd checked ("use this schema"), set all other versions to Automatic (unechecked). Restart Visual studio and warnings are gone.
My issue is that I cannot select a build process template after migrating to TFS/VS2012.
I managed to google and find one article which suggest the same problem here,
Possible Bug
Any ideas how I can get the dropdown to load the Build Process Templates or why they may not be getting loaded?
Also, I am able to click New->Copy Template, and copy successfully, but it never populates the dropdown list after accepting.
Possibly the same issue
I recently ran into the same problem but not related to upgrading the server. We were not able to see build process templates when trying to add a new build definition. We are in TFS 2012. This team project also appeared not to have any build definitions. That was expected though because we had not yet used the TFS builds on this team project.
The problem was caused by someone with admin rights setting the "View build definition" and the "View Builds" access rights to Deny for everyone.
By just setting that back to allow on the TFS group, we suddenly could see the build definitions and also were able to select build process templates.
It was really strange that it let us add new build process templates, but we couldn't select them.
Sooo...
I was finally able to get the templates loading by doing the following.
Unmapped the entire TFS project which had been mapped in a sub folder and not at the root.
Deleted files from disk completely
Remapped the TFS project, this time from the root TFS project level
Accepted the "get"
After doing this my build definitions loaded and worked. (Seems to be a mapping issue...bug...)
This may be an extream solution and I am still not sure what happened but it now works.
Recently I've faced this strange problem:
I changed a ribbon for Invoice entity on the development environment, exported the solution as managed, imported this solution to another environment, published it and nothing happens.
I checked the customization.xml file and found all my changes there.
Next, I checked the solution.xml and found that RibbonDiffXml root component is included inside the solution.
But when I checked Ribbon* tables inside SQL database, I found that relevant commands and rules were not updated.
Does anyone can assist me in solving this issue?
Try This tool whcih is the best way to edit Ribbon.
https://community.dynamics.com/crm/b/crmmusings/archive/2012/09/12/crm-2011-ribbon-workbench-getting-guids-from-selected-records-in-the-grid.aspx#.UeZA-o3WWzQ
It is working with RU 12
This is my first azure project and I'm not sure if I'm doing something wrong.
I'm trying to get some configuration inside an MVC 3 webrole and for this I'm using:
RoleEnvironment.GetConfigurationSettingValue(KeyName)
When I run the application on the emulator i get his error:
BC30451: 'RoleEnvironment' is not declared. It may be inaccessible due to its protection level.
I tried to add the full namespace like this:
Microsoft.WindowsAzure.ServiceRuntime.RoleEnvironment.GetConfigurationSettingValue(KeyName)
And I get this error:
BC30456: 'ServiceRuntime' is not a member of 'WindowsAzure'.
However, I can access the RoleEnvironment inside the "OnStart" event of the WebRole class.
So, is it the expected behavior? If yes, how am I supposed to read configuration through the whole project?
Thanks in advance;
Have you added a reference to the Microsoft.WindowsAzure.ServiceRuntime assembly in your MVC project?
http://msdn.microsoft.com/en-us/library/microsoft.windowsazure.serviceruntime.roleenvironment.aspx
I started a new solution based on seanost suggestion and it worked well, so I figured the problem wasn't VS. After a few try and errors I finally found a solution, I just don't have an explanation for it :-)
Under my MVC project I have a folder called "App_Code".
Since i come from web forms development I'm use to the name so I created this folder to keep some classes. If I try to access "RoleEnviroment" from a class inside this folder the project compiles but won't even open, no matter what I try to access it will throw the same error.
If I rename the folder or move the files to another folder (let's say "Code"), it just works.
As I said before, I just don't know why it happens (and it doesn;t really matter now :-)
FYI, if you're using Visual Studio's Azure templates, references to the following namespaces are included by default, so it's not necessary to set Copy Local to true:
Microsoft.WindowsAzure.Diagnostics
Microsoft.WindowsAzure.ServiceRuntime
Microsoft.WindowsAzure.StorageClient
To make sure Visual Studio and the SDK is installed correctly, you should be able to do the following: Create a new MVC3 Azure project, add a using directive for the ServiceRuntime library in your Home controller, then add the following code in the Index action:
ViewBag.configValue = RoleEnvironment.GetConfigurationSettingValue("Microsoft.WindowsAzure.Plugins.Diagnostics.ConnectionString");
return View();
Then, add the following Razor syntax in the View:
<p>#ViewBag.configValue;</p>
And you should get the following result in your browser:
UseDevelopmentStorage=true
During solution deployments & Feature activation, I am facing an on/off issue where the system is unable to find & load the FeatureReceiver class. Mostly it is file not found exception (even though the assembly is there in the GAC). I checked over the net and this seems it a common issue with solutions (wsp) packaging DLL to be GACed. (But, no one has any clue or solution!)
What is the recommendation and guideline to fix this issue? We are setting the flag to reset IIS in my solution definition - but that does not seem to help. The issue is more prevalent in multi-M farms.
Thanks
This is a general problem in SharePoint in cause of the "SharePoint 2010 Timer Service". Because this one caches the wsp's and during the deployment or feature activation old references will occurres this error!
So try the following link. I hope this solution will help you.
http://msscorner.de/en/2011/10/27/sharepoint-deployment-failed-to-create-receiver-object-from-assembly/
First try the solution linked to by Falco...
If that does not help, try this:
Open the event-receiver file created by sharepoint
Compare the GUID above the event-receiver-class with the one stated in the stack-trace "...class=7g3562-438dn4...
If it does not match:
Copy the content of the class
Delete the file
Create a new file by right-clicking the feature -> add new event reciever
Pass the content
First thing, you dont need to give iisreset as your wsp deployment would have already done that.
Can you check if the assembly name, version, public token specified in the feature.xml is same at the actual assembly that is deployed in gac? I am thinking there is mismatch in assembly signature