Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Final Bundle of VS Changes #231

Merged
merged 6 commits into from
Aug 31, 2016
Merged

Final Bundle of VS Changes #231

merged 6 commits into from
Aug 31, 2016

Conversation

mrucker
Copy link
Contributor

@mrucker mrucker commented Aug 23, 2016

Prof. Gerber,

Here are a few final changes to get sensus fully integrated into the Microsoft's VS IDE.

The big thing was I had the wrong build configuration so I was building all the projects. This meant Sensus.UiTest was building, and it didn't have up to date packages with the other projects. I now have the build configuration set correctly on my windows machine. However, since I'd already gotten the project up to date I went ahead and committed the package changes.

The other change in this bundle was explicitly setting the memory available for the JRE. I guess the default JRE settings on Windows are different from Mac because out of the box I hit an OME when spinning up the Android emulator. I explicitly set the memory reservation to 1 GB and no longer have any issues.

I thought I'd just go ahead and push these up by themselves so we can merge them by themselves. That way, in the future, when I'm doing actual changes the diffs will look cleaner and won't include a bunch of extra stuff.

<DebugType>full</DebugType>
<Optimize>false</Optimize>
<OutputPath>bin\Debug\</OutputPath>
<DefineConstants>DEBUG;TRACE</DefineConstants>
<ErrorReport>prompt</ErrorReport>
<WarningLevel>4</WarningLevel>
<AndroidLinkMode>None</AndroidLinkMode>
<AndroidSupportedAbis>armeabi;armeabi-v7a;x86</AndroidSupportedAbis>
<AndroidSupportedAbis>armeabi,armeabi-v7a,x86</AndroidSupportedAbis>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given the casing difference on line 28 and the use of commas rather than semicolons on line 36, will this still build on OSX?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah,

I tested in XS on my iMac. All these changes were just automatically done by Visual Studio so I left them as is.

Interestingly (and fortunately in my opinion), Xamarin Studio doesn't revert them back to the old format.

@MatthewGerber MatthewGerber merged commit 7a1550d into predictive-technology-laboratory:develop Aug 31, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants