[{"data":1,"prerenderedAt":367},["ShallowReactive",2],{"article-keep-nuget-packages-out-of-tfs-source-control":3},{"article":4,"tags":152,"previous":167,"next":268},{"id":5,"title":6,"author":7,"body":8,"createdAt":140,"description":141,"extension":142,"img":143,"meta":144,"navigation":145,"path":146,"seo":147,"stem":148,"tags":149,"updatedAt":140,"__hash__":151},"articles\u002Farticles\u002Fkeep-nuget-packages-out-of-tfs-source-control.md","Keep Nuget Packages Out of TFS (Source Control)",null,{"type":9,"value":10,"toc":138},"minimark",[11,28,31,34,37,40,88,91,94,97,100,103,114,117,126,134],[12,13,14],"p",{},[15,16,19],"a",{"style":17,"href":18},"display: none;","\u002Farticles\u002Fimages\u002Fopen-live-writer-keep-nuget-packages-out-of-tfs-source-co_8714-tfs3_2.png",[20,21],"img",{"style":22,"title":23,"src":24,"alt":23,"width":25,"height":26,"border":27},"background-image: none; padding-top: 0px; padding-left: 0px; display: inline; padding-right: 0px; border-width: 0px;","tfs3","\u002Farticles\u002Fimagesopen-live-writer-keep-nuget-packages-out-of-tfs-source-co_8714-tfs3_thumb.png",240,135,0,[12,29,30],{},"Historically, we had kept our Nuget packages in Team Foundation Server (version control). Due to the recent consistency and stability of Nuget I am starting to move towards excluding Nuget packages from TFS Source control. They just are not required anymore and Visual Studio can very quickly restore from the internet packages locally on your workstation\u002Fbuild server very quickly now.",[12,32,33],{},"So, how do we setup both Visual Studio and TFS to stop putting packages in TFS? Donovan Brown published a post describing the steps.",[12,35,36],{},"a) At the solution level (at same location where your sln file is located) create a folder named .nuget (do this from within Source Control Explorer)",[12,38,39],{},"b) Create a file named nuget.config and put this within the .nuget folder. This file should have the following content.",[41,42,47],"pre",{"className":43,"code":44,"language":45,"meta":46,"style":46},"language-xml shiki shiki-themes github-light github-dark","\u003C?xml version=\"1.0\" encoding=\"utf-8\"?>\n\u003Cconfiguration> \n    \u003Csolution> \n        \u003Cadd key=\"disableSolutionControlIntegration\" value=\"true\">\u003C\u002Fadd>\n    \u003C\u002Fsolution>\n\u003C\u002Fconfiguration>\n","xml","",[48,49,50,58,64,70,76,82],"code",{"__ignoreMap":46},[51,52,55],"span",{"class":53,"line":54},"line",1,[51,56,57],{},"\u003C?xml version=\"1.0\" encoding=\"utf-8\"?>\n",[51,59,61],{"class":53,"line":60},2,[51,62,63],{},"\u003Cconfiguration> \n",[51,65,67],{"class":53,"line":66},3,[51,68,69],{},"    \u003Csolution> \n",[51,71,73],{"class":53,"line":72},4,[51,74,75],{},"        \u003Cadd key=\"disableSolutionControlIntegration\" value=\"true\">\u003C\u002Fadd>\n",[51,77,79],{"class":53,"line":78},5,[51,80,81],{},"    \u003C\u002Fsolution>\n",[51,83,85],{"class":53,"line":84},6,[51,86,87],{},"\u003C\u002Fconfiguration>\n",[12,89,90],{},"c) Create a file .tfignore and put at the solution level also. Within this text file put a single word packages",[12,92,93],{},"So at this point, you have a directory .nuget with the nuget.config file within it, and also a text file .tfignore at the solution level. Remove any packages that have been put in source control previously and check in.",[12,95,96],{},"At this point, close Visual Studio and restart.",[12,98,99],{},"Build the solution locally and all should be good, do a check in and if everything is good the packages folder is not checked in. Tada Essentially, we are putting things in place to tell Visual Studio not to check in packages AND we are telling TFS not to check in the packages folder.\nBoth the config file and the .tfignore files are needed.",[12,101,102],{},"My solution folder looks like",[12,104,105],{},[15,106,108],{"href":107},"\u002Farticles\u002Fimages\u002Fopen-live-writer-keep-nuget-packages-out-of-tfs-source-co_8714-image_2.png",[20,109],{"style":22,"title":110,"src":111,"alt":110,"width":112,"height":113,"border":27},"image","\u002Farticles\u002Fimages\u002Fopen-live-writer-keep-nuget-packages-out-of-tfs-source-co_8714-image_thumb.png",436,104,[12,115,116],{},"Reference:",[12,118,119,122],{},[15,120],{"title":121,"href":121},"http:\u002F\u002Fdonovanbrown.com\u002Fpost\u002FHow-to-keep-packages-folder-out-of-TFVC",[15,123,121],{"href":121,"rel":124},[125],"nofollow",[12,127,128,131],{},[15,129],{"title":130,"href":130},"https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=BfKcTX8NxAQ",[15,132,130],{"href":130,"rel":133},[125],[135,136,137],"style",{},"html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":46,"searchDepth":60,"depth":60,"links":139},[],"2017-02-24T07:48:53.130Z","Historically, we had kept our Nuget packages in Team Foundation Server (version control).  Due to the recent consistency and stability of Nuget I am starting to move towards excluding Nuget packages from TFS Source control.  They just are not required anymore and Visual Studio can very quickly restore from the internet packages locally on your workstation\u002Fbuild server very quickly now.","md","\u002Farticles\u002Fimages\u002Fopen-live-writer-keep-nuget-packages-out-of-tfs-source-co_8714-tfs3_thumb.png",{},true,"\u002Farticles\u002Fkeep-nuget-packages-out-of-tfs-source-control",{"title":6,"description":141},"articles\u002Fkeep-nuget-packages-out-of-tfs-source-control",[150],"teamfoundationserver","7RYOC6n0dlrpGmS5Zj2PwVk1brKlHnvXsy7VkN0m97w",[153],{"id":154,"title":155,"body":156,"description":160,"extension":142,"img":161,"meta":162,"name":150,"navigation":145,"path":163,"seo":164,"stem":165,"__hash__":166},"tags\u002Ftags\u002Fteamfoundationserver.md","Teamfoundationserver",{"type":9,"value":157,"toc":158},[],{"title":46,"searchDepth":60,"depth":60,"links":159},[],"Team Foundation Server (often abbreviated to TFS) is a Microsoft product that provides tools and technologies designed to help teams collaborate and orchestrate their efforts to finish projects or create a product. It enables DevOps capabilities covering the entire application lifecycle","https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1598313183973-4effcded8d5e?ixlib=rb-1.2.1&ixid=eyJhcHBfaWQiOjEyMDd9&auto=format&fit=crop&w=675&q=80",{},"\u002Ftags\u002Fteamfoundationserver",{"description":160},"tags\u002Fteamfoundationserver","CEZSgtqpsn_JuGubePK9lUUC42p0YpLGI5j3KuMwrSY",{"id":168,"title":169,"author":7,"body":170,"createdAt":259,"description":260,"extension":142,"img":227,"meta":261,"navigation":145,"path":262,"seo":263,"stem":264,"tags":265,"updatedAt":259,"__hash__":267},"articles\u002Farticles\u002Fforms-master-detail-template.md","Xamarin Forms Master Detail Template",{"type":9,"value":171,"toc":257},[172,175,186,193,208,213,216,219,230,239],[12,173,174],{},"The current Xamarin Forms master detail template is broken. You will get an error like Error CS0101 The namespace 'already contains a definition for",[12,176,177,178,185],{},"The fix..(thank you ",[15,179,184],{"href":180,"target":181,"rel":182},"https:\u002F\u002Fforums.xamarin.com\u002Fprofile\u002F120906\u002FKymPhillpotts.3866","_blank",[183],"noopener","Kym Phillpotts",")",[187,188,189],"ol",{},[190,191,192],"li",{},"It would appear, that the added pages have the wrong namespace. So change the namespace on the added pages",[194,195,196,199,202,205],"ul",{},[190,197,198],{},"Page1.xaml.cs - change the Namespace to be just MyApp",[190,200,201],{},"Page1Detail.xaml.cs - Change the namespace to be just MyApp",[190,203,204],{},"Page1Master.xaml.cs - Change the namespace to be just MyApp",[190,206,207],{},"Page1MenuItem.cs - Change the namespace to \"MyApp\"",[187,209,210],{"start":60},[190,211,212],{},"I also noticed that in the Page1Master.xaml.cs it is incorrectly referencing the MenuItems.  It says Page1MenuItems = new ObservableCollection...Change that to be justMenuItems = new ObservableCollection...",[12,214,215],{},"No you can go to your App.Xaml.xs and set the Page1 as the master page:",[12,217,218],{},"eg.MainPage = new MyApp.Page1()",[12,220,221],{},[15,222,224],{"href":223},"\u002Farticle\u002Fimages\u002Fopen-live-writer-70a95c1575c8_decb-image_2.png",[20,225],{"style":226,"title":110,"src":227,"alt":110,"width":228,"height":229,"border":27},"background-image: none; padding-top: 0px; padding-left: 0px; display: inline; padding-right: 0px; border: 0px;","\u002Farticles\u002Fimages\u002Fopen-live-writer-70a95c1575c8_decb-image_thumb.png",428,296,[12,231,232,233,236],{},"Reference: ",[15,234],{"title":235,"href":235},"https:\u002F\u002Fforums.xamarin.com\u002Fdiscussion\u002F89346\u002Fforms-master-detail-page-generation-is-broken",[15,237,235],{"href":235,"rel":238},[125],[12,240,241,242,245,248,251,254],{},"Also there are bugs in Bugzilla for both of these:",[243,244],"br",{},[15,246],{"href":247},"https:\u002F\u002Fbugzilla.xamarin.com\u002Fshow_bug.cgi?id=53020",[15,249,247],{"href":247,"rel":250},[125],[15,252],{"href":253},"https:\u002F\u002Fbugzilla.xamarin.com\u002Fshow_bug.cgi?id=53021",[15,255,253],{"href":253,"rel":256},[125],{"title":46,"searchDepth":60,"depth":60,"links":258},[],"2017-03-14T13:20:03.000Z","The current Xamarin Forms master detail template is broken.  You will get an error like Error CS0101 The namespace 'already contains a definition for.",{},"\u002Farticles\u002Fforms-master-detail-template",{"title":169,"description":260},"articles\u002Fforms-master-detail-template",[266],"xamarin","INsVAI3syQmOBP5U9aqAwo-8SVPG9zLItscvwFjbZ8Y",{"id":269,"title":270,"author":271,"body":272,"createdAt":360,"description":7,"extension":142,"img":284,"meta":361,"navigation":145,"path":362,"seo":363,"stem":364,"tags":365,"updatedAt":360,"__hash__":366},"articles\u002Farticles\u002Fno-ios-simulator-or-device-appear-on-visual-studio.md","No IOS simulator or device appear on Visual Studio","[object Object]",{"type":9,"value":273,"toc":358},[274,287,294,296,308,311,322,338,346,349],[12,275,276],{},[15,277,280],{"style":278,"href":279},"display: none","\u002Farticles\u002Fimages\u002Fopen-live-writer-i_c801-xamarinios_2.png",[20,281],{"title":282,"style":283,"border":27,"alt":282,"src":284,"width":285,"height":286},"xamarinios","border-left-width: 0px; border-right-width: 0px; background-image: none; border-bottom-width: 0px; padding-top: 0px; padding-left: 0px; display: inline; padding-right: 0px; border-top-width: 0px","\u002Farticles\u002Fimages\u002Fopen-live-writer-i_c801-xamarinios_thumb.png",147,128,[12,288,289,290],{},"Ok, once again – I open a Xamarin Forms app, ensure I have the latest Xamarin Forms version in each of the PCL, Android and IOS projects. The project rebuild works for the PCL and Android projects and fails for the IOS. The error… ",[291,292,293],"em",{},"No valid iOS code signing keys found in keychain.",[291,295],{},[12,297,298,307],{},[291,299,300,301,304],{},"You need to request a codesigning certificate from\n",[15,302],{"href":303},"https:\u002F\u002Fdeveloper.apple.com",[15,305,303],{"href":303,"rel":306},[125]," What’s going on…I first look to ensure my Mac agent is connected yep, perform a clean and rebuild of each project..same error. The solution for me…. Open the dialog “Xamarin Mac Agent” – right click on the connect Mac – choose ‘Disconnect’. After disconnection – select the Mac and ‘Connect’…waiting (aha …it won’t connect, this could be the problem) Nope – didn’t think it would be this easy. I was able to use the ‘show simulator’ option within vs.net and the simulator popped open on the Mac. I opened another project to see if this issue was related to the specific project. Nope. The 2nd project I opened had the same issue, where in the ‘Device’ list the was no option for ‘iphone simulator’.",[12,309,310],{},"I then proceed to open Xamarin Studio on the Mac (currently I am using the Beta channel as this was necessary to work with Visual Studio 2017). There is an update and it started to download. Here is to more hope that this solves the issue.",[12,312,313],{},[15,314,316],{"href":315},"\u002Farticles\u002Fimages\u002Fopen-live-writer-i_c801-image_2.png",[20,317],{"title":110,"style":318,"border":27,"alt":110,"src":319,"width":320,"height":321},"border-top: 0px; border-right: 0px; background-image: none; border-bottom: 0px; padding-top: 0px; padding-left: 0px; border-left: 0px; display: inline; padding-right: 0px","\u002Farticles\u002Fimages\u002Fopen-live-writer-i_c801-image_thumb.png",229,160,[12,323,324,325,329,330],{},"This update on the Mac will move it up to ",[15,326,328],{"href":327,"target":181},"https:\u002F\u002Freleases.xamarin.com\u002Frelease-candidate-cycle-9-rc6-refresh\u002F","Xamarin Studio 6.2.0"," I tried to find the IOS Simulator after this update. Still nothing. I removed all mac agents, restarted vs.net 2017 a couple times, still nothing. I opened up another project and magically this time the ‘iphone simulator’ option was available. Why…no idea..(this product is going to kill me)\n",[15,331,333],{"href":332},"\u002Farticles\u002Fimages\u002Fopen-live-writer-i_c801-image_4.png",[20,334],{"title":110,"style":318,"border":27,"alt":110,"src":335,"width":336,"height":337},"\u002Farticles\u002Fimages\u002Fimages\u002Fopen-live-writer-i_c801-image_thumb_1.png",479,36,[12,339,340,341,345],{},"So now I am thinking there is a difference between the 2 projects. Why would I have the simulator option in one but not the other? This is really messed up. So I open the project that does not have the ‘iphonesimulator’ option, I can see within Configuration Manager that this option exists ",[342,343,344],"strong",{},"and ","I can connect, build, deploy to Mac simulator.",[12,347,348],{},"Well this scenario is new to me…no idea.",[12,350,351],{},[15,352,354],{"href":353},"\u002Farticles\u002Fimages\u002Fopen-live-writer-i_c801-image_6.png",[20,355],{"title":110,"style":318,"border":27,"alt":110,"src":356,"width":25,"height":357},"\u002Farticles\u002Fimages\u002Fopen-live-writer-i_c801-image_thumb_2.png",171,{"title":46,"searchDepth":60,"depth":60,"links":359},[],"2017-02-18T08:07:02.3200000-05:00",{},"\u002Farticles\u002Fno-ios-simulator-or-device-appear-on-visual-studio",{"title":270,"description":7},"articles\u002Fno-ios-simulator-or-device-appear-on-visual-studio",[266],"4n4VwoebArTKwJ97QT4guPzoyBnHAnofJjW9sIKPOVM",1781574768616]