Trying to get LassoLab (which is an Eclipse based IDE for lasso) to work on Windows 7.
I'm running into trouble launching a run configuration. Set it up per video here:
http://www.youtube.com/watch?v=zMTQklE3Mu0
but it does not work.
I have Lasso 9 server with IIS installed and it runs fine. Is anyone is doing Lasso development on Windows?
LassoTalk list is very Mac centric and I'm not getting any help there.
OK, so here's the answer for the benefit of others looking (now that via comments it's confirmed that was the issue):
When you created your new "lasso: project using the wizard, Configure your interpreter.
If you use the "search" the it will find it if installed.
This only needs to be done the first time you create a new project in Lasso Lab after installing Lasso 9 :)
Related
I have installed the WIndows 10 Divio App as per the Divio Tutorial but when I select setup a project it hangs at Preparing logs... in the shell on the desktop and cannot see logs are anyway to investigate this. I have tried the solution in this question here How to debug problems with the Divio app?
However, this does not work, any help would be appreicated.
Managed to fix this, I did it by following the guide here:
https://divio-cloud-developer-handbook.readthedocs.io/en/latest/introduction/01-installation.html
Essentially installed everything via the command line and then once that was running I could then sync the Divio app to the project folder which in turn allowed me to use the Divio app. Total PITA but it worked :)
I am using asp.net core 2.2 and Visual Studio 2019. The containers my application are running on are Debian (one of the official aspnet:2.2 docker images)
So my situation is this. I have an application that consists of 4 microservices running in docker containers and I'm seeing very high cpu usage on the containers nodes when this is under load. What I would like to do is profile the executing code to get an idea where this resource use is happening.
As a starting point I thought I would simply get some profiling running on my local development environment, just to get an idea of what the execution looks like in general. Although in production this runs in Kubernetes I do have a development environment that uses docker compose and I find the Visual Studio Docker tools to be fairly good.
I was hoping to use some of the visual studio profiling tools. I was able to install VSDBG on one of my locally running containers and connect to it with VS BUT in the diagnostic pane I see "the diagnostic tools window does not support the current debugging configuration". I've also tried just running the project from VS using docker compose but I see the same message when I hit a breakpoint. I'm not finding much out there about how to do this.
I also tried getting profiling going using perfcollect but after I generated the trace and opened it with perfviewer I was getting a parsing error when trying to view the cpu stacks . Still not sure what's going on there. I did find an old closed issue on their github describing what I am seeing but there was a fairly recent comment from someone saying they were seeing it with the latest version so maybe it's a regression.
So.. after all this .. my question is this. Are either of the above approaches viable? Is there a better way to achieve this? I'm interested in any way someone has had success viewing some code profiling of a .net core 2.2 application running on a linux docker container. All I really want to do is be able to see where in my code the execution time is going and what resources are being consumed. As I've mentioned I'm not finding much out there when I Google for this and I seem to keep hitting walls. If anyone had any advice or direction on a approach here I would really appreciate it. Thanks much!
Are you open to upgrading to .Net Core 3.0 (.Net Core 2.2 is going out of support in a few days: 12/23/2019)
If you're open to that you can take advantage of the new tool dotnet-trace which supports running in a linux container and can be used with the tools in Visual Studio.
Here are the steps I used to add it to my project:
Change your base image to use the sdk image (needed to install the tool).
Add installing the tool to the image:
RUN dotnet tool install --global dotnet-trace
ENV PATH $PATH:/root/.dotnet/tools
Alternatively if you don’t want to add it in your image you can run the following commands in a running container (as long as it as based on the SDK image):
dotnet tool install --global dotnet-trace
export PATH="$PATH:/root/.dotnet/tools"
Start the project without debugging (Ctrl+F5)
Use the Containers Tool Window to open a terminal window
Run the command:
dotnet-trace collect --process-id $(pidof dotnet) --providers Microsoft-DotNETCore-SampleProfiler
When you are done collecting press enter or Ctrl+C to end the collection
This will crate a file called “trace.nettrace”
By default that /app folder that file would be created in is volume mapped to your project folder. You can open the file from there in VS.
I'm getting crazy with this problem. I got in my hands a Windows XP embedded and I need to install Framework .NET3.0 and I tried everything in my mind. I've been reading a lot of wXPe and everybody says that you have to take the XPe Rollout 1.0 from your tools and remake the image.
This is my biggest problem, I didn't have any of this tools, I just have a computer with wXPe installed and I need to install my software and I don't have any kind of feedback of who have done it.
I spend a lot of time to understand the ewf and finally I get disabled. But now, I need .NET3.0 and once I get unpacked I can continue with the installation, it seems freezed, I can't continue with the installation.
I've tried to install .NET2.0, it unpacks but suddently stops.
Any idea?! I'm start thinking that is impossible without rebulding the image, but at this time, this is not an option.
Thanks!
Did you manage to get .Net framework installed on your XP Embedded image?
The problem with XP embedded is, if you leave one component out while building your image then some features/programs won't work or install.
I had the same problem with one of my XP embedded images and I figured out that I had to add the .Net framework 2 component in order to install .Net framework 3 on the image. A website I find handy is this one, there's sld's on the website you can use, if you don't have the platform builder, I will be able to help you to build a new image
I am trying to create a dev box for SharePoint 2010 Server utilizing the following:
http://blogs.msdn.com/b/cjohnson/archive/2010/10/28/announcing-sharepoint-easy-setup-for-developers.aspx
So first of all this is new to me. I understand that these are instructions are for dual boot in Windows Native, but I am more interested in using a VHD/image of the OS to run on VMWare.
I have tried creating an image of a running virtual machine with sysprep tool, but hit a dead end with capturing the image to a file that I can reference within the running machine to run the scripts against.
I took a look at Diskpart on TechNet, but as I am new to this, I am not sure this is what I want to do?
I tried installing to the local host (virtual machine that is running) and am getting an error there also; fails at Windows Identity Framework.
It is a clean install of Windows 7 (literally nothing else), and the UAC has been disabled.
Is there any insite, help, or advice anyone can provide me regarding this? I would really appreciate it as I have to get working on the development aspects of SP (workflows, web parts,etc), and need a dev env, and I can't seem to get anywhere with this.
Thanks
Justin
I've got Parallels 6 running VS2010 under Windows 7 on my Macbook Pro. I'm trying to run my .NET 4.0 MVC 3 web site (debug/release) using the VS default web server and I keep getting the following error: 'An error occurred loading a configuration file: Failed to start monitoring changes to path\to\web.config'. I saw this post here, but the solution does not apply (indeed it does not appear to be a fix for my particular problem) Any ideas?
I just ran into this myself. It has to do with the way Parallels sets up sharing of documents between OSX and Windows. I don't know how to fix the problem itself, but an easy workaround is to move your projects directory outside the Documents folder. I created C:\Projects\ and everything runs fine from there. Hope this helps.